Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcf14b3bd2f3627c987d09a3ec3a0ab54260b131c62e3e5c32f6c0d5deb83838

Tx prefix hash: 8eb7109c51d93aab9ec3a251a9e49ad032bb9780f2214ed6c49c0d6a3bc49809
Tx public key: f62093de09db2ace38fe02cda797d6ad06e819d9b29b5d8900db398bc95303d5
Timestamp: 1728410896 Timestamp [UCT]: 2024-10-08 18:08:16 Age [y:d:h:m:s]: 00:030:02:24:16
Block: 1127289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21469 RingCT/type: yes/0
Extra: 01f62093de09db2ace38fe02cda797d6ad06e819d9b29b5d8900db398bc95303d5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e4c6d4e11dac60131ff1cb744393cfe0bca96faaa6a903fe7fad8a961003d09 0.600000000000 1610090 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": 1127299, "vin": [ { "gen": { "height": 1127289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e4c6d4e11dac60131ff1cb744393cfe0bca96faaa6a903fe7fad8a961003d09" } } ], "extra": [ 1, 246, 32, 147, 222, 9, 219, 42, 206, 56, 254, 2, 205, 167, 151, 214, 173, 6, 232, 25, 217, 178, 155, 93, 137, 0, 219, 57, 139, 201, 83, 3, 213, 2, 17, 0, 0, 0, 5, 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