Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1597bd1bafa26d2d89796c17f83e830bb761e49c260562e7e8f705c1eb6dee53

Tx prefix hash: 72629a5548310509f4ae10d9679e298a8f90aab1e667a1404d76e12fe768f311
Tx public key: 13b9c2e0de2d06ee9e2cecb13bb53cd9873bb88058a174cfe0fdb1e8ace3a338
Timestamp: 1695139596 Timestamp [UCT]: 2023-09-19 16:06:36 Age [y:d:h:m:s]: 01:267:18:40:50
Block: 851640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 452449 RingCT/type: yes/0
Extra: 0113b9c2e0de2d06ee9e2cecb13bb53cd9873bb88058a174cfe0fdb1e8ace3a33802110000000133af99f4000000000000000000

1 output(s) for total of 0.925045728000 dcy

stealth address amount amount idx
00: a6d59acfcd2c64ff004b4f3a25722e805bb166da80227649613d8c7c9d6077fb 0.925045728000 1305436 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": 851650, "vin": [ { "gen": { "height": 851640 } } ], "vout": [ { "amount": 925045728, "target": { "key": "a6d59acfcd2c64ff004b4f3a25722e805bb166da80227649613d8c7c9d6077fb" } } ], "extra": [ 1, 19, 185, 194, 224, 222, 45, 6, 238, 158, 44, 236, 177, 59, 181, 60, 217, 135, 59, 184, 128, 88, 161, 116, 207, 224, 253, 177, 232, 172, 227, 163, 56, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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