Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 566a1a2e82ec2dd3e889cfd6d7eb44935ba595b55f44f7b1f4015050847879d2

Tx prefix hash: 2e82a9515418c18b5bc7132b3b3519e5e98b3302d411df650035cf1a95c02bb9
Tx public key: 720d41fee870c712a743a0d53e2729efbfe8347f973e7f543370738aff41d2cd
Timestamp: 1700518661 Timestamp [UCT]: 2023-11-20 22:17:41 Age [y:d:h:m:s]: 01:345:13:36:41
Block: 896047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505863 RingCT/type: yes/0
Extra: 01720d41fee870c712a743a0d53e2729efbfe8347f973e7f543370738aff41d2cd021100000001faf35c9c000000000000000000

1 output(s) for total of 0.659210796000 dcy

stealth address amount amount idx
00: 6bee95f16c91c61ed7345c8490e72e74c28c56b87c06c542ea66100c94019b2e 0.659210796000 1352298 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": 896057, "vin": [ { "gen": { "height": 896047 } } ], "vout": [ { "amount": 659210796, "target": { "key": "6bee95f16c91c61ed7345c8490e72e74c28c56b87c06c542ea66100c94019b2e" } } ], "extra": [ 1, 114, 13, 65, 254, 232, 112, 199, 18, 167, 67, 160, 213, 62, 39, 41, 239, 191, 232, 52, 127, 151, 62, 127, 84, 51, 112, 115, 138, 255, 65, 210, 205, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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