Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ff0535b1445d93025534fb7c11470aa44b5853ad12d9d87aa371b76202482a8

Tx prefix hash: 230abdf04045624624c766d06c8f7b8d4d09b91f23ec14e676bf11f3b2236276
Tx public key: 7514f1a833c4275c461fb726fa4dbce81e02625beaf07b4c3ca0e140dd89f0e8
Timestamp: 1711800685 Timestamp [UCT]: 2024-03-30 12:11:25 Age [y:d:h:m:s]: 00:228:21:22:18
Block: 989604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163832 RingCT/type: yes/0
Extra: 017514f1a833c4275c461fb726fa4dbce81e02625beaf07b4c3ca0e140dd89f0e80211000000100011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af2069a31169c60eb1434fa944326ea4b1324f144843caf8531292f6542f1cb3 0.600000000000 1449903 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": 989614, "vin": [ { "gen": { "height": 989604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af2069a31169c60eb1434fa944326ea4b1324f144843caf8531292f6542f1cb3" } } ], "extra": [ 1, 117, 20, 241, 168, 51, 196, 39, 92, 70, 31, 183, 38, 250, 77, 188, 232, 30, 2, 98, 91, 234, 240, 123, 76, 60, 160, 225, 64, 221, 137, 240, 232, 2, 17, 0, 0, 0, 16, 0, 17, 5, 91, 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