Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86840a72c03282b5a4b5ac44c49c208e4079bfd480d7f8519d03a2db00b0cace

Tx prefix hash: 9b49958d45d93cedd2b63caed95dca82edc9f99ff565b715bea72f97f6b5a90c
Tx public key: 5ce212062a603e4fb873d923de04f6d3f5372f22353fe8dbcbe97d1e31f61606
Timestamp: 1627513163 Timestamp [UCT]: 2021-07-28 22:59:23 Age [y:d:h:m:s]: 03:289:23:36:55
Block: 302813 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 979512 RingCT/type: yes/0
Extra: 015ce212062a603e4fb873d923de04f6d3f5372f22353fe8dbcbe97d1e31f616060211000000244acd6ddc000000000000000000

1 output(s) for total of 60.905331832000 dcy

stealth address amount amount idx
00: 93feb853f556f36ef0b2d037475792fb30b455f744a323db02f4adc3ba88e498 60.905331832000 632172 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": 302823, "vin": [ { "gen": { "height": 302813 } } ], "vout": [ { "amount": 60905331832, "target": { "key": "93feb853f556f36ef0b2d037475792fb30b455f744a323db02f4adc3ba88e498" } } ], "extra": [ 1, 92, 226, 18, 6, 42, 96, 62, 79, 184, 115, 217, 35, 222, 4, 246, 211, 245, 55, 47, 34, 53, 63, 232, 219, 203, 233, 125, 30, 49, 246, 22, 6, 2, 17, 0, 0, 0, 36, 74, 205, 109, 220, 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