Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6f83389219e1ccc4fd0ca53e00bc3816ba0a6f651e9c29df99c3052f6a657c4

Tx prefix hash: 8256c9389ebda7af366f39a74039e6f72d560a9798045983631805ae4ea7d1c4
Tx public key: aa14c54c61a4008859d9933e8fdecbf28595a77212a386e6af4c8c32187d0894
Timestamp: 1700975761 Timestamp [UCT]: 2023-11-26 05:16:01 Age [y:d:h:m:s]: 01:168:17:38:46
Block: 899828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381786 RingCT/type: yes/0
Extra: 01aa14c54c61a4008859d9933e8fdecbf28595a77212a386e6af4c8c32187d0894021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.640466300000 dcy

stealth address amount amount idx
00: 2e3f3a1756e3ce6f6c8c0931f19790b52005aee510490354ca388f83e5765c35 0.640466300000 1356293 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": 899838, "vin": [ { "gen": { "height": 899828 } } ], "vout": [ { "amount": 640466300, "target": { "key": "2e3f3a1756e3ce6f6c8c0931f19790b52005aee510490354ca388f83e5765c35" } } ], "extra": [ 1, 170, 20, 197, 76, 97, 164, 0, 136, 89, 217, 147, 62, 143, 222, 203, 242, 133, 149, 167, 114, 18, 163, 134, 230, 175, 76, 140, 50, 24, 125, 8, 148, 2, 17, 0, 0, 0, 1, 230, 210, 127, 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