Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 553e9ecb637dfa85febcfb9061dd38256e100d3a4ba216601dddcc0f28a16b17

Tx prefix hash: 4e32bac7002270fef29c42eaff45bd86b96e9bd0afe4bae4284b41293e43352d
Tx public key: 776c2c0bad6d377ff91b4e5aa21b0ccc38d0853137fcb7060806fadc5cc3b292
Timestamp: 1721853224 Timestamp [UCT]: 2024-07-24 20:33:44 Age [y:d:h:m:s]: 01:109:04:09:13
Block: 1072913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336533 RingCT/type: yes/0
Extra: 01776c2c0bad6d377ff91b4e5aa21b0ccc38d0853137fcb7060806fadc5cc3b29202110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: daee52d253669436f8afc6d5fbcded4b244f38a8cec6aaf5bcd4df1818ccb7d8 0.600000000000 1545410 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": 1072923, "vin": [ { "gen": { "height": 1072913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "daee52d253669436f8afc6d5fbcded4b244f38a8cec6aaf5bcd4df1818ccb7d8" } } ], "extra": [ 1, 119, 108, 44, 11, 173, 109, 55, 127, 249, 27, 78, 90, 162, 27, 12, 204, 56, 208, 133, 49, 55, 252, 183, 6, 8, 6, 250, 220, 92, 195, 178, 146, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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