Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1b5f43a17f64e27c7ae7ba1dcc363ddbf38101c53e31d57eab91615b4befb5c

Tx prefix hash: 98bc21e26d4d1778cec6fb4bd276cfa666d6e96499ca5564abf2d9cc6eac3cb3
Tx public key: fc9b85e6733cf965056390bcf37f11d5bd87d8d7cbf28e67d9cd0fc9dd25a164
Timestamp: 1702697951 Timestamp [UCT]: 2023-12-16 03:39:11 Age [y:d:h:m:s]: 01:136:11:31:46
Block: 914111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358687 RingCT/type: yes/0
Extra: 01fc9b85e6733cf965056390bcf37f11d5bd87d8d7cbf28e67d9cd0fc9dd25a16402110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6e7f8f91ed4d1d9347dd811b4379a9ffdbe6b183e6c067a46f0640cba91ab31 0.600000000000 1371395 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": 914121, "vin": [ { "gen": { "height": 914111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6e7f8f91ed4d1d9347dd811b4379a9ffdbe6b183e6c067a46f0640cba91ab31" } } ], "extra": [ 1, 252, 155, 133, 230, 115, 60, 249, 101, 5, 99, 144, 188, 243, 127, 17, 213, 189, 135, 216, 215, 203, 242, 142, 103, 217, 205, 15, 201, 221, 37, 161, 100, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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