Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 792a3b0c42106ccaaef197517f2e0c42f44238657424d6c04c332cdb3bfdd688

Tx prefix hash: 866e8a7c834a461cced00da0acf963a57eb80e7c48d2a162838a2d3cd0adca90
Tx public key: a1605ffa27b9749bd4ecc3038052b570eb03920c78d1d4058a0febad876b83a2
Timestamp: 1634392518 Timestamp [UCT]: 2021-10-16 13:55:18 Age [y:d:h:m:s]: 02:213:11:54:44
Block: 354264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 669394 RingCT/type: yes/0
Extra: 01a1605ffa27b9749bd4ecc3038052b570eb03920c78d1d4058a0febad876b83a202110000000dfdc024ec000000000000000000

1 output(s) for total of 41.131706043000 dcy

stealth address amount amount idx
00: 9bfb5898d12be5e1c522dec9f88e7e70f62896253f2f4e1a11bb77141fa504a9 41.131706043000 723684 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": 354274, "vin": [ { "gen": { "height": 354264 } } ], "vout": [ { "amount": 41131706043, "target": { "key": "9bfb5898d12be5e1c522dec9f88e7e70f62896253f2f4e1a11bb77141fa504a9" } } ], "extra": [ 1, 161, 96, 95, 250, 39, 185, 116, 155, 212, 236, 195, 3, 128, 82, 181, 112, 235, 3, 146, 12, 120, 209, 212, 5, 138, 15, 235, 173, 135, 107, 131, 162, 2, 17, 0, 0, 0, 13, 253, 192, 36, 236, 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