Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53d86cde16e03e4f3f1dcb17d5057e46e1c1a25577bc0dc1ff3db90fc0e96da1

Tx prefix hash: 816af5db908139174dfc8967d33690301cce4689d302ab11f19707d7aba75cd5
Tx public key: a86f50250fe3ece5dbeeb88b10c06229fd522d07ccbfd4bb40478137bfd1f4a2
Timestamp: 1636574907 Timestamp [UCT]: 2021-11-10 20:08:27 Age [y:d:h:m:s]: 03:161:11:11:30
Block: 371622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 893786 RingCT/type: yes/0
Extra: 01a86f50250fe3ece5dbeeb88b10c06229fd522d07ccbfd4bb40478137bfd1f4a20211000000086a2c97e6000000000000000000

1 output(s) for total of 36.029848691000 dcy

stealth address amount amount idx
00: 03290071d815fb19b539eed4dfb2af189640d12b62e60dc96b88a49bfd6bc1c9 36.029848691000 753032 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": 371632, "vin": [ { "gen": { "height": 371622 } } ], "vout": [ { "amount": 36029848691, "target": { "key": "03290071d815fb19b539eed4dfb2af189640d12b62e60dc96b88a49bfd6bc1c9" } } ], "extra": [ 1, 168, 111, 80, 37, 15, 227, 236, 229, 219, 238, 184, 139, 16, 192, 98, 41, 253, 82, 45, 7, 204, 191, 212, 187, 64, 71, 129, 55, 191, 209, 244, 162, 2, 17, 0, 0, 0, 8, 106, 44, 151, 230, 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