Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b83c36bae23d7c1db0eae822e91695586cac8909f5ffadc956b498cd5350ef1

Tx prefix hash: dc9a0c0d15d71b63c2fbc04f826f55969833c5072dec06aa6ec8356b4babf7f1
Tx public key: b18d01b6d49f0da2ca321a66d84acd3ac753a00514021b2885f9faf8c29b0ff0
Timestamp: 1724276594 Timestamp [UCT]: 2024-08-21 21:43:14 Age [y:d:h:m:s]: 01:079:14:13:15
Block: 1093019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315329 RingCT/type: yes/0
Extra: 01b18d01b6d49f0da2ca321a66d84acd3ac753a00514021b2885f9faf8c29b0ff0021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f9130b30846898747ab5b9892e41350065b4e93929636618980b5faed4ed953 0.600000000000 1567880 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": 1093029, "vin": [ { "gen": { "height": 1093019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f9130b30846898747ab5b9892e41350065b4e93929636618980b5faed4ed953" } } ], "extra": [ 1, 177, 141, 1, 182, 212, 159, 13, 162, 202, 50, 26, 102, 216, 74, 205, 58, 199, 83, 160, 5, 20, 2, 27, 40, 133, 249, 250, 248, 194, 155, 15, 240, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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