Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 765ba16336745a125f4ab52410db23734ad8af3055be86f9aaf476c8a3ce796e

Tx prefix hash: c80e809e6fd6b1e695d7dc5cd5f14f9ada6fac802773cc1972c54f14a8b0a298
Tx public key: eb79bb418bf7136350cbbe470d3fb669fe97f781df0a2a4997d039586fca7558
Timestamp: 1702506607 Timestamp [UCT]: 2023-12-13 22:30:07 Age [y:d:h:m:s]: 01:158:06:47:19
Block: 912523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374294 RingCT/type: yes/0
Extra: 01eb79bb418bf7136350cbbe470d3fb669fe97f781df0a2a4997d039586fca755802110000000ffaf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e709416359667f523dfcb886e692d2f4f5f8b1157db6c5c8a030a5b6820f2fc4 0.600000000000 1369751 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": 912533, "vin": [ { "gen": { "height": 912523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e709416359667f523dfcb886e692d2f4f5f8b1157db6c5c8a030a5b6820f2fc4" } } ], "extra": [ 1, 235, 121, 187, 65, 139, 247, 19, 99, 80, 203, 190, 71, 13, 63, 182, 105, 254, 151, 247, 129, 223, 10, 42, 73, 151, 208, 57, 88, 111, 202, 117, 88, 2, 17, 0, 0, 0, 15, 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