Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02001e319046bc3ac36c6171a6ad55f9dab37a1a2c2eb9576d1eaa6f1711f855

Tx prefix hash: be1153895259e1e47c38f2f3728e6d024772a18670d52620e3892272f81fd359
Tx public key: 4c84d757cdb21b3130dd7e4e5ba699dafd6fd8d7bbae568e07a52ccb60d9e878
Timestamp: 1699910055 Timestamp [UCT]: 2023-11-13 21:14:15 Age [y:d:h:m:s]: 01:364:15:27:53
Block: 891000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 519521 RingCT/type: yes/0
Extra: 014c84d757cdb21b3130dd7e4e5ba699dafd6fd8d7bbae568e07a52ccb60d9e87802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.685089206000 dcy

stealth address amount amount idx
00: 0c85a6600085c1493096c79cb757cc39c4c1989079ecedb2df0215ce786cf915 0.685089206000 1347035 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": 891010, "vin": [ { "gen": { "height": 891000 } } ], "vout": [ { "amount": 685089206, "target": { "key": "0c85a6600085c1493096c79cb757cc39c4c1989079ecedb2df0215ce786cf915" } } ], "extra": [ 1, 76, 132, 215, 87, 205, 178, 27, 49, 48, 221, 126, 78, 91, 166, 153, 218, 253, 111, 216, 215, 187, 174, 86, 142, 7, 165, 44, 203, 96, 217, 232, 120, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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