Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a44a90e7233763bfc38d43ac1b991f01fea3717ec2fc398e6d27b780686c9dc

Tx prefix hash: 01276184a21c975ea6e233a49d504ff7beb3440215808dfb98dc8e5cf9f01ac4
Tx public key: f1ca3562217c57ab0c1429ff94aa599226a2c4f9a4bbab0f84188c99ecb610bf
Timestamp: 1750075951 Timestamp [UCT]: 2025-06-16 12:12:31 Age [y:d:h:m:s]: 00:157:15:52:33
Block: 1306226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110466 RingCT/type: yes/0
Extra: 01f1ca3562217c57ab0c1429ff94aa599226a2c4f9a4bbab0f84188c99ecb610bf02110000000bbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f20032c2516ab4d77d5d8c2131534edd36c27b7e064072a02c00e6f56517235 0.600000000000 1793829 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": 1306236, "vin": [ { "gen": { "height": 1306226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f20032c2516ab4d77d5d8c2131534edd36c27b7e064072a02c00e6f56517235" } } ], "extra": [ 1, 241, 202, 53, 98, 33, 124, 87, 171, 12, 20, 41, 255, 148, 170, 89, 146, 38, 162, 196, 249, 164, 187, 171, 15, 132, 24, 140, 153, 236, 182, 16, 191, 2, 17, 0, 0, 0, 11, 191, 81, 178, 162, 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