Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de45acfb18ab8146d537e16287b9a3d131f617e903e65f6b52a778a90fd20ff8

Tx prefix hash: 8b382905ffe571a61fd7dd12c108248ee2b94dce20bb4344ec57036f80ebc239
Tx public key: 833a0d453e8987cc60ea0424a6bfa2c197cb405399de1d61a53c9573b228e71c
Timestamp: 1740672582 Timestamp [UCT]: 2025-02-27 16:09:42 Age [y:d:h:m:s]: 00:262:11:16:47
Block: 1228477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185341 RingCT/type: yes/0
Extra: 01833a0d453e8987cc60ea0424a6bfa2c197cb405399de1d61a53c9573b228e71c021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c21411e75b5ddff3c36352bad58cf55c8d6813f216fbe21ae2295357e8cb11f 0.600000000000 1715358 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": 1228487, "vin": [ { "gen": { "height": 1228477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c21411e75b5ddff3c36352bad58cf55c8d6813f216fbe21ae2295357e8cb11f" } } ], "extra": [ 1, 131, 58, 13, 69, 62, 137, 135, 204, 96, 234, 4, 36, 166, 191, 162, 193, 151, 203, 64, 83, 153, 222, 29, 97, 165, 60, 149, 115, 178, 40, 231, 28, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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