Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 363f0cb5e02fe4ea0c14ed60ef87927398908b68f07107b1fa8959e6ddc3de3a

Tx prefix hash: 67a50b7ff6d5745078ddf2191a596d65789a96aa7b5e1c00ab69fe565ecfe5df
Tx public key: c1fb8e40c261128641a6d4970f6f9574333761805b0512e68e6ae0e8c8df31af
Timestamp: 1581243211 Timestamp [UCT]: 2020-02-09 10:13:31 Age [y:d:h:m:s]: 04:324:03:17:32
Block: 61196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123837 RingCT/type: yes/0
Extra: 01c1fb8e40c261128641a6d4970f6f9574333761805b0512e68e6ae0e8c8df31af0211000000148a2ee0d9000000000000000000

1 output(s) for total of 384.798229303000 dcy

stealth address amount amount idx
00: 2806e6fed02d6c1e3d51131e5afd3623a2e5a0caa778f41fc54a378364315374 384.798229303000 112778 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": 61206, "vin": [ { "gen": { "height": 61196 } } ], "vout": [ { "amount": 384798229303, "target": { "key": "2806e6fed02d6c1e3d51131e5afd3623a2e5a0caa778f41fc54a378364315374" } } ], "extra": [ 1, 193, 251, 142, 64, 194, 97, 18, 134, 65, 166, 212, 151, 15, 111, 149, 116, 51, 55, 97, 128, 91, 5, 18, 230, 142, 106, 224, 232, 200, 223, 49, 175, 2, 17, 0, 0, 0, 20, 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