Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f03e37c04bca91fbf49d6f83bf31bb70221cb5d61fcd9bb0fd51eb57d1c4b33

Tx prefix hash: 28f20a41a1c21c2691df4cfcd46569b1ef2598954afa584c12c0a5b94ed61e41
Tx public key: 8893ae994067c41887a197d4ee34ef857f6d32486e6d0440be582c0be6edd2cf
Timestamp: 1578832953 Timestamp [UCT]: 2020-01-12 12:42:33 Age [y:d:h:m:s]: 04:356:00:10:52
Block: 43958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1143931 RingCT/type: yes/0
Extra: 018893ae994067c41887a197d4ee34ef857f6d32486e6d0440be582c0be6edd2cf0211000000034943cd9f000000000000000000

1 output(s) for total of 438.899141462000 dcy

stealth address amount amount idx
00: ca22dd0a55c487256d47804cfcbfa0d3abe58d624493cf2111d130ee693434e4 438.899141462000 79807 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": 43968, "vin": [ { "gen": { "height": 43958 } } ], "vout": [ { "amount": 438899141462, "target": { "key": "ca22dd0a55c487256d47804cfcbfa0d3abe58d624493cf2111d130ee693434e4" } } ], "extra": [ 1, 136, 147, 174, 153, 64, 103, 196, 24, 135, 161, 151, 212, 238, 52, 239, 133, 127, 109, 50, 72, 110, 109, 4, 64, 190, 88, 44, 11, 230, 237, 210, 207, 2, 17, 0, 0, 0, 3, 73, 67, 205, 159, 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