Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a8034395f1194e484168df4a596ae4db6ed2063dfd4090d8012d5b38e64e5eb

Tx prefix hash: d2bf6e256195d19353bee3c43bb44b3d2596166c1fb48dece2b9061033d9bbe7
Tx public key: e06479b23980c34e22f158d3d8d7ede7f566cf6aecc7da1c2c3504ed204c22d4
Timestamp: 1744673630 Timestamp [UCT]: 2025-04-14 23:33:50 Age [y:d:h:m:s]: 00:256:23:54:19
Block: 1261599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181465 RingCT/type: yes/0
Extra: 01e06479b23980c34e22f158d3d8d7ede7f566cf6aecc7da1c2c3504ed204c22d4021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12dd13af5fd2523ccd9247884c60219c9cb2b80de6ce90b7c63c2f36c9910b05 0.600000000000 1748772 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": 1261609, "vin": [ { "gen": { "height": 1261599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12dd13af5fd2523ccd9247884c60219c9cb2b80de6ce90b7c63c2f36c9910b05" } } ], "extra": [ 1, 224, 100, 121, 178, 57, 128, 195, 78, 34, 241, 88, 211, 216, 215, 237, 231, 245, 102, 207, 106, 236, 199, 218, 28, 44, 53, 4, 237, 32, 76, 34, 212, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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