Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34b87b88a49e2d25cdb2b994b3d63748bd346df2f8931eca4fde1178f7980e92

Tx prefix hash: 611f4e40a977f0705bf3187a80fa3c81112f7ad216fee62244465d64e8cc30b8
Tx public key: 294523bf4498090155e2ace6a1414bc994bf95fd9b9cbce7fc24e8f1592f6cad
Timestamp: 1721750234 Timestamp [UCT]: 2024-07-23 15:57:14 Age [y:d:h:m:s]: 00:268:11:32:20
Block: 1072054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191815 RingCT/type: yes/0
Extra: 01294523bf4498090155e2ace6a1414bc994bf95fd9b9cbce7fc24e8f1592f6cad02110000000fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a3ea13f5fbffd091d57d570bd161b39aa0faf6d236cbdab20c40bd01e7e315e 0.600000000000 1544489 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": 1072064, "vin": [ { "gen": { "height": 1072054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a3ea13f5fbffd091d57d570bd161b39aa0faf6d236cbdab20c40bd01e7e315e" } } ], "extra": [ 1, 41, 69, 35, 191, 68, 152, 9, 1, 85, 226, 172, 230, 161, 65, 75, 201, 148, 191, 149, 253, 155, 156, 188, 231, 252, 36, 232, 241, 89, 47, 108, 173, 2, 17, 0, 0, 0, 15, 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