Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51827cf4f2552f4699abb7f30295d8c5ad643c62c30d2e463aaf3c4c3dbcd7c5

Tx prefix hash: 684c4594ebe0a4eea24e300b97d162a131b98c547e0058052c52248805f8c89f
Tx public key: 3ba36b1a03812d8627c5415a58e4f2d5d72506d37a9555967f47f0215f09f0c8
Timestamp: 1582195707 Timestamp [UCT]: 2020-02-20 10:48:27 Age [y:d:h:m:s]: 05:115:17:26:20
Block: 68773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1235812 RingCT/type: yes/0
Extra: 013ba36b1a03812d8627c5415a58e4f2d5d72506d37a9555967f47f0215f09f0c80211000000017adf42d3000000000000000000

1 output(s) for total of 363.184501703000 dcy

stealth address amount amount idx
00: ca214d1cee7f3d9798ef559c94af8090c2664c2e1cc5b61cbb99847cfa17da50 363.184501703000 126782 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": 68783, "vin": [ { "gen": { "height": 68773 } } ], "vout": [ { "amount": 363184501703, "target": { "key": "ca214d1cee7f3d9798ef559c94af8090c2664c2e1cc5b61cbb99847cfa17da50" } } ], "extra": [ 1, 59, 163, 107, 26, 3, 129, 45, 134, 39, 197, 65, 90, 88, 228, 242, 213, 215, 37, 6, 211, 122, 149, 85, 150, 127, 71, 240, 33, 95, 9, 240, 200, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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