Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d6e3af21c6d8235cd58856d8e48737813f6d22357710e5c8a8e6c42f100780d

Tx prefix hash: a47644cdca4afae62442c9d5e0828534dfc88a0c332e2d714324f524edef8f6a
Tx public key: d4bf17f6ab2fd82c5d4b75f9f1e615d39472c48ba97120e28c2533460d569696
Timestamp: 1699543854 Timestamp [UCT]: 2023-11-09 15:30:54 Age [y:d:h:m:s]: 01:131:10:24:56
Block: 887974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355131 RingCT/type: yes/0
Extra: 01d4bf17f6ab2fd82c5d4b75f9f1e615d39472c48ba97120e28c2533460d56969602110000000533af99f4000000000000000000

1 output(s) for total of 0.701089598000 dcy

stealth address amount amount idx
00: a6ca88504767a50419c83704eb50aae80b1013d99e5679be5c1d486506b10999 0.701089598000 1343889 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": 887984, "vin": [ { "gen": { "height": 887974 } } ], "vout": [ { "amount": 701089598, "target": { "key": "a6ca88504767a50419c83704eb50aae80b1013d99e5679be5c1d486506b10999" } } ], "extra": [ 1, 212, 191, 23, 246, 171, 47, 216, 44, 93, 75, 117, 249, 241, 230, 21, 211, 148, 114, 196, 139, 169, 113, 32, 226, 140, 37, 51, 70, 13, 86, 150, 150, 2, 17, 0, 0, 0, 5, 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