Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26fc252cedaef0a98ebf5cc90baba2497e0e697080dbb48571465f11dfc57934

Tx prefix hash: eae4ecd7b785799fb7878d4032283befe524cc1de8151d79ca21f570a9f03d42
Tx public key: f07c7cc9d6e1c363952009a3be22ef418c4f1ceee63e60fd33b76b4f8b86044d
Timestamp: 1726465455 Timestamp [UCT]: 2024-09-16 05:44:15 Age [y:d:h:m:s]: 00:115:21:55:53
Block: 1111153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82887 RingCT/type: yes/0
Extra: 01f07c7cc9d6e1c363952009a3be22ef418c4f1ceee63e60fd33b76b4f8b86044d02110000000291e13c04000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 038152ac0782ede850c8cdc8bfd517a801c24f813f275a37581300f3f5e7ca4a 0.608000000000 1590012 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": 1111163, "vin": [ { "gen": { "height": 1111153 } } ], "vout": [ { "amount": 608000000, "target": { "key": "038152ac0782ede850c8cdc8bfd517a801c24f813f275a37581300f3f5e7ca4a" } } ], "extra": [ 1, 240, 124, 124, 201, 214, 225, 195, 99, 149, 32, 9, 163, 190, 34, 239, 65, 140, 79, 28, 238, 230, 62, 96, 253, 51, 183, 107, 79, 139, 134, 4, 77, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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