Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb34ef42bf85544488829fdffa765937e98b4fa9c4e0496b3f06d9eb543e4bfc

Tx prefix hash: 098dcf4ab49c2a918c08abeb8cdb4b81708193d31db1770759465b9544d16de2
Tx public key: b45f669b27308ffe7d63e7ae4492797c84bfc4ca1f4e9f65a8895d8b90282846
Timestamp: 1707959672 Timestamp [UCT]: 2024-02-15 01:14:32 Age [y:d:h:m:s]: 00:333:01:09:50
Block: 957728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238425 RingCT/type: yes/0
Extra: 01b45f669b27308ffe7d63e7ae4492797c84bfc4ca1f4e9f65a8895d8b9028284602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddf0dce88ab9a5cf3726b19390a968f65a19195aeaea5b8c66ac259455cea98a 0.600000000000 1417077 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": 957738, "vin": [ { "gen": { "height": 957728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddf0dce88ab9a5cf3726b19390a968f65a19195aeaea5b8c66ac259455cea98a" } } ], "extra": [ 1, 180, 95, 102, 155, 39, 48, 143, 254, 125, 99, 231, 174, 68, 146, 121, 124, 132, 191, 196, 202, 31, 78, 159, 101, 168, 137, 93, 139, 144, 40, 40, 70, 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