Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43f60d6f12c483f2723ce56f5b21b63e205abfc7aa3a8bdf893fa6bd3abd20ee

Tx prefix hash: a1d4bb457075bab7cfa4589fd2da7bac8110a533e10f9c2d13d3ba95d912787e
Tx public key: 0f0ba5887b949493fddb7298125db1d6368c37d4bb06f504921c2cc306f36b47
Timestamp: 1703208160 Timestamp [UCT]: 2023-12-22 01:22:40 Age [y:d:h:m:s]: 01:067:04:39:08
Block: 918339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309116 RingCT/type: yes/0
Extra: 010f0ba5887b949493fddb7298125db1d6368c37d4bb06f504921c2cc306f36b4702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7b3f3ae661f10e8263b9ae4bbb594a2827ca03de0158a29701c9253e37c4b9e 0.600000000000 1375981 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": 918349, "vin": [ { "gen": { "height": 918339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7b3f3ae661f10e8263b9ae4bbb594a2827ca03de0158a29701c9253e37c4b9e" } } ], "extra": [ 1, 15, 11, 165, 136, 123, 148, 148, 147, 253, 219, 114, 152, 18, 93, 177, 214, 54, 140, 55, 212, 187, 6, 245, 4, 146, 28, 44, 195, 6, 243, 107, 71, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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