Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1699ec8f081306a7808fbabac78757ef5d2c23a69debca17ed3de2f0c4bbf8d6

Tx prefix hash: 96420a766aebf8c1f1fe467ddc0c30c513d30b391448a74f5249e65ae2428eb9
Tx public key: d7af79eec9d94bdfde1d1ce1398a6fd2b15761fec91622ac741b1b7c90342595
Timestamp: 1584923175 Timestamp [UCT]: 2020-03-23 00:26:15 Age [y:d:h:m:s]: 05:050:18:41:10
Block: 86954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1193833 RingCT/type: yes/0
Extra: 01d7af79eec9d94bdfde1d1ce1398a6fd2b15761fec91622ac741b1b7c90342595021100000091e5e30634000000000000000000

1 output(s) for total of 316.144828079000 dcy

stealth address amount amount idx
00: 9eda136ca72471fcadf2f6f9db74200cb68d179d683860dc3f575bbdb8149bd9 316.144828079000 156814 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": 86964, "vin": [ { "gen": { "height": 86954 } } ], "vout": [ { "amount": 316144828079, "target": { "key": "9eda136ca72471fcadf2f6f9db74200cb68d179d683860dc3f575bbdb8149bd9" } } ], "extra": [ 1, 215, 175, 121, 238, 201, 217, 75, 223, 222, 29, 28, 225, 57, 138, 111, 210, 177, 87, 97, 254, 201, 22, 34, 172, 116, 27, 27, 124, 144, 52, 37, 149, 2, 17, 0, 0, 0, 145, 229, 227, 6, 52, 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