Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83f12c59572959318f32fbe9b8bc4b520501f1121489fc48b60b71a4381135bd

Tx prefix hash: 240c9e2ee7a49087792873039ae36e11f6a573d3c1b1bea0f99d5e4690ad7ef5
Tx public key: eabf4620f5b6a3d6bf7126f73826227a9f16361edc38129721c21f2eb26960e5
Timestamp: 1717800859 Timestamp [UCT]: 2024-06-07 22:54:19 Age [y:d:h:m:s]: 00:266:16:14:12
Block: 1039324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190559 RingCT/type: yes/0
Extra: 01eabf4620f5b6a3d6bf7126f73826227a9f16361edc38129721c21f2eb26960e5021100000002d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 304ab6e1d6b745159c294c7be97f20b6e9ca621d5e3b0ea0937c111bc2d1a86c 0.600000000000 1507957 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": 1039334, "vin": [ { "gen": { "height": 1039324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "304ab6e1d6b745159c294c7be97f20b6e9ca621d5e3b0ea0937c111bc2d1a86c" } } ], "extra": [ 1, 234, 191, 70, 32, 245, 182, 163, 214, 191, 113, 38, 247, 56, 38, 34, 122, 159, 22, 54, 30, 220, 56, 18, 151, 33, 194, 31, 46, 178, 105, 96, 229, 2, 17, 0, 0, 0, 2, 215, 73, 245, 17, 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