Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cab4a19dbe2f4d229e900196455904c9093a51b9cecaee7935cbbd24b8a8ebb

Tx prefix hash: cd5b109d4c18e574d1b85ac43b330fdd16a7a30c04e6858aafdd6305f358d107
Tx public key: b550ab12266ca0fb04e84d935d32ffee8d5a907f3a072e4de069f12205d6be08
Timestamp: 1581951113 Timestamp [UCT]: 2020-02-17 14:51:53 Age [y:d:h:m:s]: 05:016:04:39:44
Block: 66931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1164514 RingCT/type: yes/0
Extra: 01b550ab12266ca0fb04e84d935d32ffee8d5a907f3a072e4de069f12205d6be080211000000058a2ee0d9000000000000000000

1 output(s) for total of 368.324510878000 dcy

stealth address amount amount idx
00: 9d9928e3b6f29ded457ca6edfb6857d6727f58c0100dbc6e5b54fb244ce1ca3f 368.324510878000 123192 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": 66941, "vin": [ { "gen": { "height": 66931 } } ], "vout": [ { "amount": 368324510878, "target": { "key": "9d9928e3b6f29ded457ca6edfb6857d6727f58c0100dbc6e5b54fb244ce1ca3f" } } ], "extra": [ 1, 181, 80, 171, 18, 38, 108, 160, 251, 4, 232, 77, 147, 93, 50, 255, 238, 141, 90, 144, 127, 58, 7, 46, 77, 224, 105, 241, 34, 5, 214, 190, 8, 2, 17, 0, 0, 0, 5, 138, 46, 224, 217, 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