Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f89fbeb0194e1c1a0d73613a52538be7e9bcc99f113b68a0bb469ee693b88562

Tx prefix hash: 52c3769e4f861f512c73a08775679bf3c95b23c2eb34576fe1757ee646be45d6
Tx public key: 3d59e38b6000d449bb86cee2f3889d3d6c6e57e528ca37fb9448a05894040855
Timestamp: 1735605560 Timestamp [UCT]: 2024-12-31 00:39:20 Age [y:d:h:m:s]: 00:169:06:00:10
Block: 1186802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120670 RingCT/type: yes/0
Extra: 013d59e38b6000d449bb86cee2f3889d3d6c6e57e528ca37fb9448a0589404085502110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8abce4873ea6da5ce6250fd61a628b672d52628103e042b0f0b5ab5a72b5a6e4 0.600000000000 1673287 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": 1186812, "vin": [ { "gen": { "height": 1186802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8abce4873ea6da5ce6250fd61a628b672d52628103e042b0f0b5ab5a72b5a6e4" } } ], "extra": [ 1, 61, 89, 227, 139, 96, 0, 212, 73, 187, 134, 206, 226, 243, 136, 157, 61, 108, 110, 87, 229, 40, 202, 55, 251, 148, 72, 160, 88, 148, 4, 8, 85, 2, 17, 0, 0, 0, 10, 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