Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18ab5fdcad94addbd41f79ab1ee48961a0d1290e1d55203cf721b7b80ee75d2e

Tx prefix hash: 112c2bc842ffe6e3dd346b07860479d3e604e411c02974abe8cdb0f021ee5c0f
Tx public key: 2a153539752f2df770dc5f010671b2bb067405c6dab50c4e77bcc3c408fef1e2
Timestamp: 1740831255 Timestamp [UCT]: 2025-03-01 12:14:15 Age [y:d:h:m:s]: 00:336:04:40:22
Block: 1229787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237957 RingCT/type: yes/0
Extra: 012a153539752f2df770dc5f010671b2bb067405c6dab50c4e77bcc3c408fef1e2021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40352f84843452b6c6b041c4d52935876841206b86239ffe82f5c0e301e78ca4 0.600000000000 1716676 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": 1229797, "vin": [ { "gen": { "height": 1229787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40352f84843452b6c6b041c4d52935876841206b86239ffe82f5c0e301e78ca4" } } ], "extra": [ 1, 42, 21, 53, 57, 117, 47, 45, 247, 112, 220, 95, 1, 6, 113, 178, 187, 6, 116, 5, 198, 218, 181, 12, 78, 119, 188, 195, 196, 8, 254, 241, 226, 2, 17, 0, 0, 0, 7, 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