Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba5f236b4a942818947ad40d8d429ef8f90d8aded62d5a8cbddbbe8f601007cc

Tx prefix hash: b6a332db09f9d55ec25ffccba34c3f8b2ab7b805b2f232425febb1a7f8ec742e
Tx public key: f72a6d8b9a21da1aa3474963346c9a3beaf6a65d93cb7772f71fa894a5beec72
Timestamp: 1580858771 Timestamp [UCT]: 2020-02-04 23:26:11 Age [y:d:h:m:s]: 05:029:08:37:56
Block: 58671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1173151 RingCT/type: yes/0
Extra: 01f72a6d8b9a21da1aa3474963346c9a3beaf6a65d93cb7772f71fa894a5beec720211000000028a2ee0d9000000000000000000

1 output(s) for total of 392.282958325000 dcy

stealth address amount amount idx
00: 1fc085dcd885ac9e06238991e0c1f678f1e8851d2225a5f0767537d1d498b371 392.282958325000 108435 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": 58681, "vin": [ { "gen": { "height": 58671 } } ], "vout": [ { "amount": 392282958325, "target": { "key": "1fc085dcd885ac9e06238991e0c1f678f1e8851d2225a5f0767537d1d498b371" } } ], "extra": [ 1, 247, 42, 109, 139, 154, 33, 218, 26, 163, 71, 73, 99, 52, 108, 154, 59, 234, 246, 166, 93, 147, 203, 119, 114, 247, 31, 168, 148, 165, 190, 236, 114, 2, 17, 0, 0, 0, 2, 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