Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 129e6e1967f3bd877bb15ecc22972a01e78473adf076db2de6e05fc495b3e97c

Tx prefix hash: 25dd44623a17bb589c514d31e38c9a3f628114c6b31ff880dffc89f1d1774426
Tx public key: dbc2004b6e3c630c8a4034d39e9d133328255fbaa5aa068a6e56fe146f0e9fa3
Timestamp: 1723811787 Timestamp [UCT]: 2024-08-16 12:36:27 Age [y:d:h:m:s]: 00:284:04:15:41
Block: 1089160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203012 RingCT/type: yes/0
Extra: 01dbc2004b6e3c630c8a4034d39e9d133328255fbaa5aa068a6e56fe146f0e9fa302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58f208fe301fe504fb53a1e912579573e81d2db25d1c780225dc58fd514351b1 0.600000000000 1563779 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": 1089170, "vin": [ { "gen": { "height": 1089160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58f208fe301fe504fb53a1e912579573e81d2db25d1c780225dc58fd514351b1" } } ], "extra": [ 1, 219, 194, 0, 75, 110, 60, 99, 12, 138, 64, 52, 211, 158, 157, 19, 51, 40, 37, 95, 186, 165, 170, 6, 138, 110, 86, 254, 20, 111, 14, 159, 163, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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