Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91695b3a716a24397bdfdc14c6186182260816e068d097dcec591634c26a11c1

Tx prefix hash: a933c6eeea50143065896bb7cd41cc79ba70156470cafe1d6f1389a29d095b3e
Tx public key: 9afd9a0aad16c7102287cac4a020e5d51e0fe269ffa86f70d2cc530d02d3f478
Timestamp: 1699057567 Timestamp [UCT]: 2023-11-04 00:26:07 Age [y:d:h:m:s]: 01:069:10:04:42
Block: 884140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310823 RingCT/type: yes/0
Extra: 019afd9a0aad16c7102287cac4a020e5d51e0fe269ffa86f70d2cc530d02d3f47802110000000333af99f4000000000000000000

1 output(s) for total of 0.721900201000 dcy

stealth address amount amount idx
00: ea538b5097ac9ff8497aba63d1d13d2f6503e0e0bfff3eddf9f6fd2dc690b7ac 0.721900201000 1339873 of 0

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": 884150, "vin": [ { "gen": { "height": 884140 } } ], "vout": [ { "amount": 721900201, "target": { "key": "ea538b5097ac9ff8497aba63d1d13d2f6503e0e0bfff3eddf9f6fd2dc690b7ac" } } ], "extra": [ 1, 154, 253, 154, 10, 173, 22, 199, 16, 34, 135, 202, 196, 160, 32, 229, 213, 30, 15, 226, 105, 255, 168, 111, 112, 210, 204, 83, 13, 2, 211, 244, 120, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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