Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8dbe431cf9ca611e5c7550f2119f30a3c35debadc40d4c084300c2c5f58dbeaa

Tx prefix hash: 53fd8acd3e8fc3465d2719c6e65a3023b54510cbac8b1d2ba22456c48cacb71d
Tx public key: 39e8440728f568cf90721bda67d28060a177069c90e44733377f4b92bdd5405b
Timestamp: 1725732723 Timestamp [UCT]: 2024-09-07 18:12:03 Age [y:d:h:m:s]: 00:218:10:21:58
Block: 1105086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155968 RingCT/type: yes/0
Extra: 0139e8440728f568cf90721bda67d28060a177069c90e44733377f4b92bdd5405b021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 717819afe6cb8ce8b734d4d7c755937220a2f9b01362e77805fd39f0f84b2f14 0.600000000000 1582423 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": 1105096, "vin": [ { "gen": { "height": 1105086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "717819afe6cb8ce8b734d4d7c755937220a2f9b01362e77805fd39f0f84b2f14" } } ], "extra": [ 1, 57, 232, 68, 7, 40, 245, 104, 207, 144, 114, 27, 218, 103, 210, 128, 96, 161, 119, 6, 156, 144, 228, 71, 51, 55, 127, 75, 146, 189, 213, 64, 91, 2, 17, 0, 0, 0, 1, 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