Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b19b7629855891474174a57e1263d940e8ace0f9f9d4da1a1b07863b5cf06936

Tx prefix hash: 68e5ab518eaf7cf06e78de1034707d1b22f85ea204de74dc98b40227695ce3f2
Tx public key: 005b5b01fea551501267aa76b51e4cffaedc21edb1a4a9b5b2a34cd320edac63
Timestamp: 1670479343 Timestamp [UCT]: 2022-12-08 06:02:23 Age [y:d:h:m:s]: 02:120:16:44:36
Block: 647889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 607956 RingCT/type: yes/0
Extra: 01005b5b01fea551501267aa76b51e4cffaedc21edb1a4a9b5b2a34cd320edac630211000000017e406890000000000000000000

1 output(s) for total of 4.377990160000 dcy

stealth address amount amount idx
00: 36457cdb9bcfd9bde7f0fcace6ad78ca70ac77dc5a80c475a9718864c86f4797 4.377990160000 1088192 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": 647899, "vin": [ { "gen": { "height": 647889 } } ], "vout": [ { "amount": 4377990160, "target": { "key": "36457cdb9bcfd9bde7f0fcace6ad78ca70ac77dc5a80c475a9718864c86f4797" } } ], "extra": [ 1, 0, 91, 91, 1, 254, 165, 81, 80, 18, 103, 170, 118, 181, 30, 76, 255, 174, 220, 33, 237, 177, 164, 169, 181, 178, 163, 76, 211, 32, 237, 172, 99, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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