Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dc3970891b08f239d7caa8337dc2dc0337cd4af27ec028d3eba1c33e42c98cf

Tx prefix hash: d9c27c7d9d6bcfe1aaf6abab963de4969d9836ceaf375a580913e9e9a0cdda32
Tx public key: 6353d300bc676a1c150d0df93fd2209c62b24e0602df4ba8c1c5be390cb33470
Timestamp: 1583747017 Timestamp [UCT]: 2020-03-09 09:43:37 Age [y:d:h:m:s]: 05:066:11:51:47
Block: 78917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1203376 RingCT/type: yes/0
Extra: 016353d300bc676a1c150d0df93fd2209c62b24e0602df4ba8c1c5be390cb33470021100000001c48ea382000000000000000000

1 output(s) for total of 336.136760703000 dcy

stealth address amount amount idx
00: 298d4c9de3b46c44f6c4c1f6a8e30b5cb231590ef547945468a2b445fc4425ed 336.136760703000 144591 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": 78927, "vin": [ { "gen": { "height": 78917 } } ], "vout": [ { "amount": 336136760703, "target": { "key": "298d4c9de3b46c44f6c4c1f6a8e30b5cb231590ef547945468a2b445fc4425ed" } } ], "extra": [ 1, 99, 83, 211, 0, 188, 103, 106, 28, 21, 13, 13, 249, 63, 210, 32, 156, 98, 178, 78, 6, 2, 223, 75, 168, 193, 197, 190, 57, 12, 179, 52, 112, 2, 17, 0, 0, 0, 1, 196, 142, 163, 130, 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