Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af64667f6c6c1c773017b732d84896a6e79628815d006f696084620073f22e22

Tx prefix hash: 214ccd354da6569ca6ce9aaa42f1e00e8735bf64aae683203d283dbdfec08e7b
Tx public key: add28706c45c2efb86e80cc2b4daf81106e8f3c21e1fa352dd5509e3fb965c39
Timestamp: 1736260127 Timestamp [UCT]: 2025-01-07 14:28:47 Age [y:d:h:m:s]: 00:086:11:53:16
Block: 1192227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61584 RingCT/type: yes/0
Extra: 01add28706c45c2efb86e80cc2b4daf81106e8f3c21e1fa352dd5509e3fb965c39021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13ebd64e114c54f91eed1f36cd9c9908e64de243fd6c0eac5ce8f00b88762f06 0.600000000000 1678776 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": 1192237, "vin": [ { "gen": { "height": 1192227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13ebd64e114c54f91eed1f36cd9c9908e64de243fd6c0eac5ce8f00b88762f06" } } ], "extra": [ 1, 173, 210, 135, 6, 196, 92, 46, 251, 134, 232, 12, 194, 180, 218, 248, 17, 6, 232, 243, 194, 30, 31, 163, 82, 221, 85, 9, 227, 251, 150, 92, 57, 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