Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 853e702773c23a22a85b8c914de355b2662d12795241ba04d84ebcd338c45500

Tx prefix hash: 0de43083fe6e2e79a85b8d692f13e903e4231d948b0487ed6b512623b6ba943b
Tx public key: a47fa5fa74a168b396f5fb1599cd3b5fd6dadf6a147f59359ccad5b3c0f731c6
Timestamp: 1577827548 Timestamp [UCT]: 2019-12-31 21:25:48 Age [y:d:h:m:s]: 04:335:00:36:55
Block: 36021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128533 RingCT/type: yes/0
Extra: 01a47fa5fa74a168b396f5fb1599cd3b5fd6dadf6a147f59359ccad5b3c0f731c6021100000190ac34bf9e000000000000000000

1 output(s) for total of 466.289703032000 dcy

stealth address amount amount idx
00: e31550e3914768c05a421ebc3f302ff75aa1683dd1b67fbd02cbdb2abeeec94e 466.289703032000 60861 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": 36031, "vin": [ { "gen": { "height": 36021 } } ], "vout": [ { "amount": 466289703032, "target": { "key": "e31550e3914768c05a421ebc3f302ff75aa1683dd1b67fbd02cbdb2abeeec94e" } } ], "extra": [ 1, 164, 127, 165, 250, 116, 161, 104, 179, 150, 245, 251, 21, 153, 205, 59, 95, 214, 218, 223, 106, 20, 127, 89, 53, 156, 202, 213, 179, 192, 247, 49, 198, 2, 17, 0, 0, 1, 144, 172, 52, 191, 158, 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