Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55565727cbc352e2339d22d0536c2c1b3fc6427aa0dcf9b1315d613ef43af9e1

Tx prefix hash: d2766c77918cabd8d09a13b73bd0f083c533b415b1e65be66bba2589e1a17b03
Tx public key: 1b14fd364c4ca96a78fbd3fb3c4f2edda8ae26d48e0cf068e031178722afa01a
Timestamp: 1576427417 Timestamp [UCT]: 2019-12-15 16:30:17 Age [y:d:h:m:s]: 04:346:18:59:47
Block: 27821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133548 RingCT/type: yes/0
Extra: 011b14fd364c4ca96a78fbd3fb3c4f2edda8ae26d48e0cf068e031178722afa01a0211000000219159db1e000000000000000000

1 output(s) for total of 496.384650394000 dcy

stealth address amount amount idx
00: 843811e4a34433e24ba9605e73b33f5dca2cb341281b968c647c9bfd2fd693cf 496.384650394000 45877 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": 27831, "vin": [ { "gen": { "height": 27821 } } ], "vout": [ { "amount": 496384650394, "target": { "key": "843811e4a34433e24ba9605e73b33f5dca2cb341281b968c647c9bfd2fd693cf" } } ], "extra": [ 1, 27, 20, 253, 54, 76, 76, 169, 106, 120, 251, 211, 251, 60, 79, 46, 221, 168, 174, 38, 212, 142, 12, 240, 104, 224, 49, 23, 135, 34, 175, 160, 26, 2, 17, 0, 0, 0, 33, 145, 89, 219, 30, 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