Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f595ab302240bccad0c2cbcb0afebe8d9ef19e0f4b09215b61090353319275ea

Tx prefix hash: b3813bc8fc36ee0bed68f888c210bcfea311bc1bfc9220dcbe14728380e37480
Tx public key: ea2e702f91b2f4d784703fc2a9f829e99a185adc7e9a61f970057ee95561e15a
Timestamp: 1730684088 Timestamp [UCT]: 2024-11-04 01:34:48 Age [y:d:h:m:s]: 00:171:19:31:26
Block: 1146050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122641 RingCT/type: yes/0
Extra: 01ea2e702f91b2f4d784703fc2a9f829e99a185adc7e9a61f970057ee95561e15a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.614080000000 dcy

stealth address amount amount idx
00: 5f3c67d1f9d8a3584a522da09c576c282e9687945fbea50145d365fe43df1818 0.614080000000 1630605 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": 1146060, "vin": [ { "gen": { "height": 1146050 } } ], "vout": [ { "amount": 614080000, "target": { "key": "5f3c67d1f9d8a3584a522da09c576c282e9687945fbea50145d365fe43df1818" } } ], "extra": [ 1, 234, 46, 112, 47, 145, 178, 244, 215, 132, 112, 63, 194, 169, 248, 41, 233, 154, 24, 90, 220, 126, 154, 97, 249, 112, 5, 126, 233, 85, 97, 225, 90, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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