Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a5e3df2f91a7ca2498cf862de37c38dac0605d7fea36e526a4b5ff585b63405

Tx prefix hash: 337604588417826600df182b01517fb6b93b0195cee81670631dc570aa9999a0
Tx public key: 01a3a9b9cad90e4f64a621254ef366e6af9b728080b788765d1a46cec54b9c27
Timestamp: 1737464726 Timestamp [UCT]: 2025-01-21 13:05:26 Age [y:d:h:m:s]: 00:149:13:50:40
Block: 1202154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106619 RingCT/type: yes/0
Extra: 0101a3a9b9cad90e4f64a621254ef366e6af9b728080b788765d1a46cec54b9c27021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 601f53d85e4a9f4f615f8c56c1230e92496c011d474b368fa119574e868cd8d4 0.600000000000 1688815 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": 1202164, "vin": [ { "gen": { "height": 1202154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "601f53d85e4a9f4f615f8c56c1230e92496c011d474b368fa119574e868cd8d4" } } ], "extra": [ 1, 1, 163, 169, 185, 202, 217, 14, 79, 100, 166, 33, 37, 78, 243, 102, 230, 175, 155, 114, 128, 128, 183, 136, 118, 93, 26, 70, 206, 197, 75, 156, 39, 2, 17, 0, 0, 0, 8, 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