Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9152e455cc8fa5c423b3358a4dc9368da99cc6c9a736a43961065b4785f2adfa

Tx prefix hash: 4963927595e66bef39473f2f1179e2288f1c1be080c80cc2e16efac68e2af52a
Tx public key: 39948d14c21212cd282bb70a5d52ffcf6db0045d690eb0c95cf92231b3f6e0b6
Timestamp: 1703767337 Timestamp [UCT]: 2023-12-28 12:42:17 Age [y:d:h:m:s]: 01:095:19:31:53
Block: 922976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329582 RingCT/type: yes/0
Extra: 0139948d14c21212cd282bb70a5d52ffcf6db0045d690eb0c95cf92231b3f6e0b602110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a7117fe29f126837bde9e66b780b16d953a4e7c291a8455bc2ff6fd142650bc 0.600000000000 1380682 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": 922986, "vin": [ { "gen": { "height": 922976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a7117fe29f126837bde9e66b780b16d953a4e7c291a8455bc2ff6fd142650bc" } } ], "extra": [ 1, 57, 148, 141, 20, 194, 18, 18, 205, 40, 43, 183, 10, 93, 82, 255, 207, 109, 176, 4, 93, 105, 14, 176, 201, 92, 249, 34, 49, 179, 246, 224, 182, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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