Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f95c98403e997453b1a3432cd2a0c3dd03fb900f5f916e7f90c42a7bff682fcc

Tx prefix hash: 28f15e503c5199db56ba22083340ae5c678439c89f5bf6d301afccd25d21fd67
Tx public key: a30510e3b4d0c36d777541acaf012011abd67c62dc9f42291033e7e5e811d415
Timestamp: 1699212231 Timestamp [UCT]: 2023-11-05 19:23:51 Age [y:d:h:m:s]: 01:186:14:12:05
Block: 885211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394574 RingCT/type: yes/0
Extra: 01a30510e3b4d0c36d777541acaf012011abd67c62dc9f42291033e7e5e811d415021100000005faf35c9c000000000000000000

1 output(s) for total of 0.716025507000 dcy

stealth address amount amount idx
00: 51a5b9952989aed5064a28007eff5ee4436398639717ba6933d4dae58e05fa57 0.716025507000 1340972 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": 885221, "vin": [ { "gen": { "height": 885211 } } ], "vout": [ { "amount": 716025507, "target": { "key": "51a5b9952989aed5064a28007eff5ee4436398639717ba6933d4dae58e05fa57" } } ], "extra": [ 1, 163, 5, 16, 227, 180, 208, 195, 109, 119, 117, 65, 172, 175, 1, 32, 17, 171, 214, 124, 98, 220, 159, 66, 41, 16, 51, 231, 229, 232, 17, 212, 21, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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