Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1113cf3585dee78bed985a8fb6a4a2c8b70a287d486393d53c6801d8b6681b4d

Tx prefix hash: d0e7818b2a7ae59700015712544702f87164c8b4bd1650bfb5a2e032365a86be
Tx public key: 370deb5f60b5dd03e5619afb5454278ef082bdbe0168f802200f1b2e6defc7e3
Timestamp: 1709243650 Timestamp [UCT]: 2024-02-29 21:54:10 Age [y:d:h:m:s]: 00:204:14:28:03
Block: 968387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146557 RingCT/type: yes/0
Extra: 01370deb5f60b5dd03e5619afb5454278ef082bdbe0168f802200f1b2e6defc7e30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3812d50d396c52bd8d6e9a790e0e41a0a76a3c7afd970f5e00a5ee4581385a3 0.600000000000 1428202 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": 968397, "vin": [ { "gen": { "height": 968387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3812d50d396c52bd8d6e9a790e0e41a0a76a3c7afd970f5e00a5ee4581385a3" } } ], "extra": [ 1, 55, 13, 235, 95, 96, 181, 221, 3, 229, 97, 154, 251, 84, 84, 39, 142, 240, 130, 189, 190, 1, 104, 248, 2, 32, 15, 27, 46, 109, 239, 199, 227, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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