Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17225236c2ff0c30639ed22649069f53c6d0656a339c391d4f03d5004417d2e4

Tx prefix hash: 7d89247129e59e1da0b1fb83515ed85413645eb9b30c9a5920fecfab4f4c4e0a
Tx public key: 8d2a74e85417117e09cc800a29bc0e1c85c0484962ec31e3b29658caff6521d9
Timestamp: 1669659983 Timestamp [UCT]: 2022-11-28 18:26:23 Age [y:d:h:m:s]: 02:137:02:49:24
Block: 641115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 619715 RingCT/type: yes/0
Extra: 018d2a74e85417117e09cc800a29bc0e1c85c0484962ec31e3b29658caff6521d9021100000003272bcc39000000000000000000

1 output(s) for total of 4.610201047000 dcy

stealth address amount amount idx
00: 0d9107ef6a5419d84ad803fe648f3c5b9c7e2b37259c1d2560df077a2d54b480 4.610201047000 1080892 of 0

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": 641125, "vin": [ { "gen": { "height": 641115 } } ], "vout": [ { "amount": 4610201047, "target": { "key": "0d9107ef6a5419d84ad803fe648f3c5b9c7e2b37259c1d2560df077a2d54b480" } } ], "extra": [ 1, 141, 42, 116, 232, 84, 23, 17, 126, 9, 204, 128, 10, 41, 188, 14, 28, 133, 192, 72, 73, 98, 236, 49, 227, 178, 150, 88, 202, 255, 101, 33, 217, 2, 17, 0, 0, 0, 3, 39, 43, 204, 57, 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