Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1ab9100c7fdf7798042e961e8a6f1cb93ae018cebcccdd59904c7bff26f6658

Tx prefix hash: 7c64072858ef99263213084b1272335df5a3766e8fa4371c0e733d02ec029083
Tx public key: 89f2c5a708dce287bbb32ecc36381e00ccb3d3116f63bb2c84d9040ed0dbcc8d
Timestamp: 1713836433 Timestamp [UCT]: 2024-04-23 01:40:33 Age [y:d:h:m:s]: 01:191:11:03:14
Block: 1006457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395480 RingCT/type: yes/0
Extra: 0189f2c5a708dce287bbb32ecc36381e00ccb3d3116f63bb2c84d9040ed0dbcc8d0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46e4432811f0ab684581c773e932859fd3597b2c32e60a1c94e8e198a4ea1a6f 0.600000000000 1467495 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": 1006467, "vin": [ { "gen": { "height": 1006457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46e4432811f0ab684581c773e932859fd3597b2c32e60a1c94e8e198a4ea1a6f" } } ], "extra": [ 1, 137, 242, 197, 167, 8, 220, 226, 135, 187, 179, 46, 204, 54, 56, 30, 0, 204, 179, 211, 17, 111, 99, 187, 44, 132, 217, 4, 14, 208, 219, 204, 141, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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