Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 258f0ae27505d0b9dc97536590663d7417a2906e64cd458f12e876ec3844dbbb

Tx prefix hash: bba11aa3c4ea170c3123c26a5e0b62920c2be11c006e471a6824257691584b5e
Tx public key: fb79d8bb1fa12ead62936f69b1a0ff967c3c0c1b44cd22649abd37c24425a4f8
Timestamp: 1643916930 Timestamp [UCT]: 2022-02-03 19:35:30 Age [y:d:h:m:s]: 03:090:22:39:56
Block: 431543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 844206 RingCT/type: yes/0
Extra: 01fb79d8bb1fa12ead62936f69b1a0ff967c3c0c1b44cd22649abd37c24425a4f802110000000637cb3088000000000000000000

1 output(s) for total of 22.809680643000 dcy

stealth address amount amount idx
00: a7830dd91c1d0d90e79c00c97a6b37e754a7fac7db1c358015784cd506f2444c 22.809680643000 841796 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": 431553, "vin": [ { "gen": { "height": 431543 } } ], "vout": [ { "amount": 22809680643, "target": { "key": "a7830dd91c1d0d90e79c00c97a6b37e754a7fac7db1c358015784cd506f2444c" } } ], "extra": [ 1, 251, 121, 216, 187, 31, 161, 46, 173, 98, 147, 111, 105, 177, 160, 255, 150, 124, 60, 12, 27, 68, 205, 34, 100, 154, 189, 55, 194, 68, 37, 164, 248, 2, 17, 0, 0, 0, 6, 55, 203, 48, 136, 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