Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 034b7e2efa4692d73ea04895aa0cf5b12173552cc1f940eb7682292858b11722

Tx prefix hash: f71acd6ba1849d6c0f2fb1e1167dd0985b9d0d711d6b08f7bdf4fa7d08e832a5
Tx public key: f9e78d3cb50129073db236c925bc22026fe91c65a802c6b4b426ed08fbdb45d3
Timestamp: 1733773017 Timestamp [UCT]: 2024-12-09 19:36:57 Age [y:d:h:m:s]: 00:106:14:46:48
Block: 1171641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75970 RingCT/type: yes/0
Extra: 01f9e78d3cb50129073db236c925bc22026fe91c65a802c6b4b426ed08fbdb45d3021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8f1c3f5d324eecc1d95cbd9720413763b8c4ae805a3f5ef1c5c4503e2bde9e1 0.600000000000 1657422 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": 1171651, "vin": [ { "gen": { "height": 1171641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8f1c3f5d324eecc1d95cbd9720413763b8c4ae805a3f5ef1c5c4503e2bde9e1" } } ], "extra": [ 1, 249, 231, 141, 60, 181, 1, 41, 7, 61, 178, 54, 201, 37, 188, 34, 2, 111, 233, 28, 101, 168, 2, 198, 180, 180, 38, 237, 8, 251, 219, 69, 211, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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