Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 298d1f8bb6c851c752c67b2ac2f2574324dba322460253a2401999c1aeb7cf2f

Tx prefix hash: 347355f7164eeffcdb6300d827b0bdc298554801040fe0530d4e8e780dc42f8a
Tx public key: f62fb173ec9d988ef7c5ce93f1fc39e2620d66c227fd8cf4c0bcc55e80d97ab7
Timestamp: 1748944260 Timestamp [UCT]: 2025-06-03 09:51:00 Age [y:d:h:m:s]: 00:216:14:30:28
Block: 1296982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152567 RingCT/type: yes/0
Extra: 01f62fb173ec9d988ef7c5ce93f1fc39e2620d66c227fd8cf4c0bcc55e80d97ab7021100000016bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31baaab471920fb9c1e51746571132d5324966fc524e7c0f9f93ec70402e72ec 0.600000000000 1784499 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": 1296992, "vin": [ { "gen": { "height": 1296982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31baaab471920fb9c1e51746571132d5324966fc524e7c0f9f93ec70402e72ec" } } ], "extra": [ 1, 246, 47, 177, 115, 236, 157, 152, 142, 247, 197, 206, 147, 241, 252, 57, 226, 98, 13, 102, 194, 39, 253, 140, 244, 192, 188, 197, 94, 128, 217, 122, 183, 2, 17, 0, 0, 0, 22, 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