Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f87418bdc35b6ceedcd3ba0286511819155f950602d6b0ce485a3b0a1e306699

Tx prefix hash: 229616703d7c28b70c6bc54d559b5821feb056176a39b035f38296aeaf2eea99
Tx public key: 6678435513d971dc85b9e33c1db018611cc7a8fb03b63e5aee7fcaefef5c43cf
Timestamp: 1737322633 Timestamp [UCT]: 2025-01-19 21:37:13 Age [y:d:h:m:s]: 00:149:01:15:46
Block: 1200976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106268 RingCT/type: yes/0
Extra: 016678435513d971dc85b9e33c1db018611cc7a8fb03b63e5aee7fcaefef5c43cf021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57bae2b160fc5c299599b46b2d134b0d1b08bb1d5481b1a934e44cd6d1177851 0.600000000000 1687623 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": 1200986, "vin": [ { "gen": { "height": 1200976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57bae2b160fc5c299599b46b2d134b0d1b08bb1d5481b1a934e44cd6d1177851" } } ], "extra": [ 1, 102, 120, 67, 85, 19, 217, 113, 220, 133, 185, 227, 60, 29, 176, 24, 97, 28, 199, 168, 251, 3, 182, 62, 90, 238, 127, 202, 239, 239, 92, 67, 207, 2, 17, 0, 0, 0, 1, 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