Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ded78cd28216c8ee1ded384a36d694136ffe37ca121ff106033670e52d2b60bc

Tx prefix hash: b1095eb7516ffcbbc4091e04ae8b10b2768e39e2f011fb5edae717860c952915
Tx public key: bdd8a7249bd2ed4ecfc82cb0ac7f0209a5083b1e7ae081f83fa9689d414fc115
Timestamp: 1681998602 Timestamp [UCT]: 2023-04-20 13:50:02 Age [y:d:h:m:s]: 01:268:09:58:16
Block: 742747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453322 RingCT/type: yes/0
Extra: 01bdd8a7249bd2ed4ecfc82cb0ac7f0209a5083b1e7ae081f83fa9689d414fc11502110000000675e3f0e9000000000000000000

1 output(s) for total of 2.123103048000 dcy

stealth address amount amount idx
00: b8bfc7a520dfdfa7df7632d09997c63758aa4ff6c3bd42dd9189104bce0e4e9f 2.123103048000 1189736 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": 742757, "vin": [ { "gen": { "height": 742747 } } ], "vout": [ { "amount": 2123103048, "target": { "key": "b8bfc7a520dfdfa7df7632d09997c63758aa4ff6c3bd42dd9189104bce0e4e9f" } } ], "extra": [ 1, 189, 216, 167, 36, 155, 210, 237, 78, 207, 200, 44, 176, 172, 127, 2, 9, 165, 8, 59, 30, 122, 224, 129, 248, 63, 169, 104, 157, 65, 79, 193, 21, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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