Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c8b842f3d376500be96237ce513e05b7fb9af2c3fc49bb264e6c30a69c3902e

Tx prefix hash: b713ab7561f0696b0a36af8d2682c8ac2f59ae88bea870737169816548510f5c
Tx public key: 631f5ae86599e6d56866fb6d42dedaa2226e8f00d408a17e7aa870522f5b0ed5
Timestamp: 1719854225 Timestamp [UCT]: 2024-07-01 17:17:05 Age [y:d:h:m:s]: 00:281:17:39:56
Block: 1056341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201316 RingCT/type: yes/0
Extra: 01631f5ae86599e6d56866fb6d42dedaa2226e8f00d408a17e7aa870522f5b0ed50211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8392e72dc6790f19f71a54eb55df53039ce31f687fab5895673472b964788d22 0.600000000000 1526754 of 15

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": 1056351, "vin": [ { "gen": { "height": 1056341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8392e72dc6790f19f71a54eb55df53039ce31f687fab5895673472b964788d22" } } ], "extra": [ 1, 99, 31, 90, 232, 101, 153, 230, 213, 104, 102, 251, 109, 66, 222, 218, 162, 34, 110, 143, 0, 212, 8, 161, 126, 122, 168, 112, 82, 47, 91, 14, 213, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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