Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7107503e72b420887bd9f387fe914cafff1ef0c3d764a14074abefb1e411849f

Tx prefix hash: 67e2b8578d6c023d81f27f6e0a74548ed57a7b50ffbec15aff3d2ef1d616bd26
Tx public key: 5de9da4cbe73ae485964baa62ad3151f63a7e6cac1f0d70794ba05c24b5d75c9
Timestamp: 1727120488 Timestamp [UCT]: 2024-09-23 19:41:28 Age [y:d:h:m:s]: 00:106:00:53:20
Block: 1116591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75815 RingCT/type: yes/0
Extra: 015de9da4cbe73ae485964baa62ad3151f63a7e6cac1f0d70794ba05c24b5d75c9021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 79fd5d772d3f02bb90e26c67867d7d5759949c5e0745908003a5f737d123e670 0.600000000000 1597126 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": 1116601, "vin": [ { "gen": { "height": 1116591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "79fd5d772d3f02bb90e26c67867d7d5759949c5e0745908003a5f737d123e670" } } ], "extra": [ 1, 93, 233, 218, 76, 190, 115, 174, 72, 89, 100, 186, 166, 42, 211, 21, 31, 99, 167, 230, 202, 193, 240, 215, 7, 148, 186, 5, 194, 75, 93, 117, 201, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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