Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 955cde488151e186b25f11dd9b1d725729ffe885e35f48be691ae60d501e62c8

Tx prefix hash: 605213ca9aad9d4b008902a3db55636c3cbebc8177f7dd731a7fdf21b3e02658
Tx public key: e3ba95d723cf925d7ab63bd6085f022a99db54e6ec1b912c17852c2c7b060560
Timestamp: 1715634180 Timestamp [UCT]: 2024-05-13 21:03:00 Age [y:d:h:m:s]: 00:130:15:22:22
Block: 1021358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93587 RingCT/type: yes/0
Extra: 01e3ba95d723cf925d7ab63bd6085f022a99db54e6ec1b912c17852c2c7b0605600211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7b1a7c965ce8604d218a9974f23f401fe269d2283aaac6a3633b2c6b98556af 0.600000000000 1485655 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1021368, "vin": [ { "gen": { "height": 1021358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7b1a7c965ce8604d218a9974f23f401fe269d2283aaac6a3633b2c6b98556af" } } ], "extra": [ 1, 227, 186, 149, 215, 35, 207, 146, 93, 122, 182, 59, 214, 8, 95, 2, 42, 153, 219, 84, 230, 236, 27, 145, 44, 23, 133, 44, 44, 123, 6, 5, 96, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8