Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b63a4f7c327706180d73f8314317ff41dfc046140466c74cc2035893db0ce66

Tx prefix hash: 85bda93bc39761db49f03d5f5644581ac26b83a91299e9dd06b66b93571856b5
Tx public key: f4e92eda4a821a5a639835c95288c7609c8b5d1c9ee8092822451729a9ac2736
Timestamp: 1658535509 Timestamp [UCT]: 2022-07-23 00:18:29 Age [y:d:h:m:s]: 02:249:03:29:03
Block: 549603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 699248 RingCT/type: yes/0
Extra: 01f4e92eda4a821a5a639835c95288c7609c8b5d1c9ee8092822451729a9ac2736021100000001a8c141c5000000000000000000

1 output(s) for total of 9.266959026000 dcy

stealth address amount amount idx
00: b3f95e1a93fa5812d83df06622dc7ac1c0dfd0b2dd5e28bf52b995d12a42555e 9.266959026000 980988 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": 549613, "vin": [ { "gen": { "height": 549603 } } ], "vout": [ { "amount": 9266959026, "target": { "key": "b3f95e1a93fa5812d83df06622dc7ac1c0dfd0b2dd5e28bf52b995d12a42555e" } } ], "extra": [ 1, 244, 233, 46, 218, 74, 130, 26, 90, 99, 152, 53, 201, 82, 136, 199, 96, 156, 139, 93, 28, 158, 232, 9, 40, 34, 69, 23, 41, 169, 172, 39, 54, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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