Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 042501a9daa32a045e6c24956526a40af476e29984c6106e3b898a49a9602014

Tx prefix hash: d2fce2c478138755f90e6579fc051d4ccf88354f908727d1a0d59c6a82b39dd1
Tx public key: 10bf6f0da1c3f13f7ddaa4d9cccdca175d960f37afa4fb5d70795bae64907f9a
Timestamp: 1725583785 Timestamp [UCT]: 2024-09-06 00:49:45 Age [y:d:h:m:s]: 01:087:17:47:27
Block: 1103855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321161 RingCT/type: yes/0
Extra: 0110bf6f0da1c3f13f7ddaa4d9cccdca175d960f37afa4fb5d70795bae64907f9a021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90699315c4b6f40303be65984dd0c6372ba87d331b126c6bcbcc3ba4e05e31da 0.600000000000 1580844 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": 1103865, "vin": [ { "gen": { "height": 1103855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90699315c4b6f40303be65984dd0c6372ba87d331b126c6bcbcc3ba4e05e31da" } } ], "extra": [ 1, 16, 191, 111, 13, 161, 195, 241, 63, 125, 218, 164, 217, 204, 205, 202, 23, 93, 150, 15, 55, 175, 164, 251, 93, 112, 121, 91, 174, 100, 144, 127, 154, 2, 17, 0, 0, 0, 7, 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