Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d92a257c55d0d1a2f975eb6d636a3d27c927f2ce80935854610f63579568036a

Tx prefix hash: 0812087e16392e58e366b71576ca18e5be9a838f65f4bce3f4d978ce65c71bb3
Tx public key: bbc8e5cc9fb134ec7fc9db67b57fe0aecfbef824dc500f0f83cd1efee482370e
Timestamp: 1736762616 Timestamp [UCT]: 2025-01-13 10:03:36 Age [y:d:h:m:s]: 00:064:04:36:05
Block: 1196391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45663 RingCT/type: yes/0
Extra: 01bbc8e5cc9fb134ec7fc9db67b57fe0aecfbef824dc500f0f83cd1efee482370e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b548c6f626c2e92500de6d88795f27ac53deacaab13bdd34169fb3d858462745 0.600000000000 1682990 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": 1196401, "vin": [ { "gen": { "height": 1196391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b548c6f626c2e92500de6d88795f27ac53deacaab13bdd34169fb3d858462745" } } ], "extra": [ 1, 187, 200, 229, 204, 159, 177, 52, 236, 127, 201, 219, 103, 181, 127, 224, 174, 207, 190, 248, 36, 220, 80, 15, 15, 131, 205, 30, 254, 228, 130, 55, 14, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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