Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f6c1dcc2e6107d817fc4a5533fdd77e4b617381e91be45f5b8ca7435716b477

Tx prefix hash: f14c0d8ccd2251d0d6333deb32afb3993c3d81a01675f6e75e9ee588b97775a7
Tx public key: cb7150f29054851950c7d699faa24c8ddd7f88c037a9f3a3f3975b0c87f468ef
Timestamp: 1737734685 Timestamp [UCT]: 2025-01-24 16:04:45 Age [y:d:h:m:s]: 00:144:02:27:59
Block: 1204379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102738 RingCT/type: yes/0
Extra: 01cb7150f29054851950c7d699faa24c8ddd7f88c037a9f3a3f3975b0c87f468ef021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6bb572bb85464f0d71705a8c0dbabc8dbe66f586ad372c37fcf4ae2c31182cc 0.600000000000 1691064 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": 1204389, "vin": [ { "gen": { "height": 1204379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6bb572bb85464f0d71705a8c0dbabc8dbe66f586ad372c37fcf4ae2c31182cc" } } ], "extra": [ 1, 203, 113, 80, 242, 144, 84, 133, 25, 80, 199, 214, 153, 250, 162, 76, 141, 221, 127, 136, 192, 55, 169, 243, 163, 243, 151, 91, 12, 135, 244, 104, 239, 2, 17, 0, 0, 0, 2, 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