Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 772441ef825f839406896893c6228e7ff04fe098fde38c048fb1732aabfbd37e

Tx prefix hash: d26da75f61057a232780b412d092353dfb5fbdd6d67484793e78db1523b9ee86
Tx public key: beb910f7d9c4d1a43897c0386912f75bdcb7df4d474140fd742fe5ae207c651e
Timestamp: 1699059617 Timestamp [UCT]: 2023-11-04 01:00:17 Age [y:d:h:m:s]: 01:166:09:17:07
Block: 884154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379921 RingCT/type: yes/0
Extra: 01beb910f7d9c4d1a43897c0386912f75bdcb7df4d474140fd742fe5ae207c651e021100000002faf35c9c000000000000000000

1 output(s) for total of 0.721823097000 dcy

stealth address amount amount idx
00: fd0e7557b5bae3d18b895dc51fb7c8ab0dd540f36ed914689411ff7aa8c1059d 0.721823097000 1339887 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": 884164, "vin": [ { "gen": { "height": 884154 } } ], "vout": [ { "amount": 721823097, "target": { "key": "fd0e7557b5bae3d18b895dc51fb7c8ab0dd540f36ed914689411ff7aa8c1059d" } } ], "extra": [ 1, 190, 185, 16, 247, 217, 196, 209, 164, 56, 151, 192, 56, 105, 18, 247, 91, 220, 183, 223, 77, 71, 65, 64, 253, 116, 47, 229, 174, 32, 124, 101, 30, 2, 17, 0, 0, 0, 2, 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