Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 873da188c0634d0a53e861d411fc126fdc284bc18ce2e51a4b0d79a1d7423649

Tx prefix hash: 02373e9c96dd2615da38f4042a8566623404b238bade1584ba165c0b07461925
Tx public key: 6f221d616cc8a3dcb17c43b2be82f09491b71b33dd40150c1a0443e0f39bc1f7
Timestamp: 1715443347 Timestamp [UCT]: 2024-05-11 16:02:27 Age [y:d:h:m:s]: 00:229:07:38:06
Block: 1019804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164107 RingCT/type: yes/0
Extra: 016f221d616cc8a3dcb17c43b2be82f09491b71b33dd40150c1a0443e0f39bc1f702110000000141ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61a4008bc75e5622c604c1e9d42c1e75d5ed30832e5873fe315000f1a8590f71 0.600000000000 1483849 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": 1019814, "vin": [ { "gen": { "height": 1019804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61a4008bc75e5622c604c1e9d42c1e75d5ed30832e5873fe315000f1a8590f71" } } ], "extra": [ 1, 111, 34, 29, 97, 108, 200, 163, 220, 177, 124, 67, 178, 190, 130, 240, 148, 145, 183, 27, 51, 221, 64, 21, 12, 26, 4, 67, 224, 243, 155, 193, 247, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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