Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee4f053d3173f708a15684cdaa3cbcaefc869fdb0aade5776994775a28a50a52

Tx prefix hash: d4738cedc3cc54b0996eb5b23d2d9b593d2282944664972a034458a18677d4b8
Tx public key: bcc8524b0d9a90eab6a4c4a814150c68bb37c75f6cc88f0a1373b864f36c39b1
Timestamp: 1719574519 Timestamp [UCT]: 2024-06-28 11:35:19 Age [y:d:h:m:s]: 00:281:03:13:59
Block: 1054027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200884 RingCT/type: yes/0
Extra: 01bcc8524b0d9a90eab6a4c4a814150c68bb37c75f6cc88f0a1373b864f36c39b10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac3e63ff753ce094ef8c92a9507ef30c32ea197e330785b3ad9953465eefca74 0.600000000000 1524386 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": 1054037, "vin": [ { "gen": { "height": 1054027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac3e63ff753ce094ef8c92a9507ef30c32ea197e330785b3ad9953465eefca74" } } ], "extra": [ 1, 188, 200, 82, 75, 13, 154, 144, 234, 182, 164, 196, 168, 20, 21, 12, 104, 187, 55, 199, 95, 108, 200, 143, 10, 19, 115, 184, 100, 243, 108, 57, 177, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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