Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e59a83c807e485f32113e76c92854e3cf0c7e88a9daf884ffe540b47fcb39bd

Tx prefix hash: 3db60c6ffdf7ab1469359f5e4dccc5e6e1f08ec9c526b6d60fbe060f8f5d35d1
Tx public key: 5f258edea9a65b44fb62124383d8b62bee09913ef51e503be54bdd7d9fb34a0e
Timestamp: 1721543909 Timestamp [UCT]: 2024-07-21 06:38:29 Age [y:d:h:m:s]: 00:174:00:26:16
Block: 1070346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124523 RingCT/type: yes/0
Extra: 015f258edea9a65b44fb62124383d8b62bee09913ef51e503be54bdd7d9fb34a0e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56a35245f3fa6cc9c14abf1a8a5e3027a9825b031e2cf74e092d19aa7ba099ab 0.600000000000 1542141 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": 1070356, "vin": [ { "gen": { "height": 1070346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56a35245f3fa6cc9c14abf1a8a5e3027a9825b031e2cf74e092d19aa7ba099ab" } } ], "extra": [ 1, 95, 37, 142, 222, 169, 166, 91, 68, 251, 98, 18, 67, 131, 216, 182, 43, 238, 9, 145, 62, 245, 30, 80, 59, 229, 75, 221, 125, 159, 179, 74, 14, 2, 17, 0, 0, 0, 3, 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