Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b8a71911593451cd729a748bbe37a292bcc2f65e570ce0a32c66149b575d70f

Tx prefix hash: f71e258517be4cd302bbc9c67a35de76e99c260ba681124210af25298de91145
Tx public key: 004d31e25e3edebcf7ef8c82125d0e9353d7248c5a478c5437f4b8e00b0f4584
Timestamp: 1713720541 Timestamp [UCT]: 2024-04-21 17:29:01 Age [y:d:h:m:s]: 01:193:14:01:25
Block: 1005488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397028 RingCT/type: yes/0
Extra: 01004d31e25e3edebcf7ef8c82125d0e9353d7248c5a478c5437f4b8e00b0f45840211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f1432f51a0f6a38d225780f3178f2e8193acb42a1acea6b0448cfb663ed5e42 0.600000000000 1466200 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": 1005498, "vin": [ { "gen": { "height": 1005488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f1432f51a0f6a38d225780f3178f2e8193acb42a1acea6b0448cfb663ed5e42" } } ], "extra": [ 1, 0, 77, 49, 226, 94, 62, 222, 188, 247, 239, 140, 130, 18, 93, 14, 147, 83, 215, 36, 140, 90, 71, 140, 84, 55, 244, 184, 224, 11, 15, 69, 132, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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