Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd637955d5ed8d47602f3857763e8c442d4b438892f49e9864523a6a2579077f

Tx prefix hash: fbe0f013472ee8ffa45a43d00fdfd6367669d0c0aadfc463d5ec54c8edc8eefe
Tx public key: 453c7d50af17ac2b9135cfd451a10a377e2b1121bbadc98803eb4553e03cd1df
Timestamp: 1700096788 Timestamp [UCT]: 2023-11-16 01:06:28 Age [y:d:h:m:s]: 01:099:17:37:30
Block: 892542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332420 RingCT/type: yes/0
Extra: 01453c7d50af17ac2b9135cfd451a10a377e2b1121bbadc98803eb4553e03cd1df021100000005c5452960000000000000000000

1 output(s) for total of 0.677076650000 dcy

stealth address amount amount idx
00: 45c3ac8f2e93e4b00a3af0939cfc89da580ae4ed557d470dcf727a029b0346da 0.677076650000 1348661 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": 892552, "vin": [ { "gen": { "height": 892542 } } ], "vout": [ { "amount": 677076650, "target": { "key": "45c3ac8f2e93e4b00a3af0939cfc89da580ae4ed557d470dcf727a029b0346da" } } ], "extra": [ 1, 69, 60, 125, 80, 175, 23, 172, 43, 145, 53, 207, 212, 81, 161, 10, 55, 126, 43, 17, 33, 187, 173, 201, 136, 3, 235, 69, 83, 224, 60, 209, 223, 2, 17, 0, 0, 0, 5, 197, 69, 41, 96, 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