Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec7fefa064869c13187f4dc33832275880d5e515103b9bda266cbebcd72d6ecb

Tx prefix hash: bc4c87fbd0a3e6ee19c4dad60242814fb44da1b2aa0938a19ffec195cfb5a371
Tx public key: 87290051c36787fd8795d3f3550e57122d4ac0e52d4730b8d7f0ce54ff2d529b
Timestamp: 1712312228 Timestamp [UCT]: 2024-04-05 10:17:08 Age [y:d:h:m:s]: 01:041:21:44:45
Block: 993791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290959 RingCT/type: yes/0
Extra: 0187290051c36787fd8795d3f3550e57122d4ac0e52d4730b8d7f0ce54ff2d529b02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41ad700ae1647b5d836844bc224b9f002edcba8a3d7f58f14def4bc777d68bad 0.600000000000 1454179 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": 993801, "vin": [ { "gen": { "height": 993791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41ad700ae1647b5d836844bc224b9f002edcba8a3d7f58f14def4bc777d68bad" } } ], "extra": [ 1, 135, 41, 0, 81, 195, 103, 135, 253, 135, 149, 211, 243, 85, 14, 87, 18, 45, 74, 192, 229, 45, 71, 48, 184, 215, 240, 206, 84, 255, 45, 82, 155, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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