Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 725b4d426821b98d73c26a6f7c16b46f25d9d9114376b306f73aa8959c9ccdbf

Tx prefix hash: 9439d12dff60714a9ab311ee56d42004a744c6aaf5b2b852c2746a00475a31de
Tx public key: a327f777a631b1f7e8c3a6bae7e534cf22c3474f5c4f598d51ae15a803070974
Timestamp: 1676278850 Timestamp [UCT]: 2023-02-13 09:00:50 Age [y:d:h:m:s]: 01:336:22:34:35
Block: 695979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501754 RingCT/type: yes/0
Extra: 01a327f777a631b1f7e8c3a6bae7e534cf22c3474f5c4f598d51ae15a80307097402110000000175e3f0e9000000000000000000

1 output(s) for total of 3.033420221000 dcy

stealth address amount amount idx
00: e46d04b34a52c18f4de39fd16def8e4d7c707898b85c7b9ae30e84e7fa322954 3.033420221000 1138940 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": 695989, "vin": [ { "gen": { "height": 695979 } } ], "vout": [ { "amount": 3033420221, "target": { "key": "e46d04b34a52c18f4de39fd16def8e4d7c707898b85c7b9ae30e84e7fa322954" } } ], "extra": [ 1, 163, 39, 247, 119, 166, 49, 177, 247, 232, 195, 166, 186, 231, 229, 52, 207, 34, 195, 71, 79, 92, 79, 89, 141, 81, 174, 21, 168, 3, 7, 9, 116, 2, 17, 0, 0, 0, 1, 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