Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7860b9d1b074d66eb6b9f143fd582d6fa5fad2cc2335634b16d15634d1a52a03

Tx prefix hash: 15dc2865a50e66f455a8414445bf8991686701e028dc2cd54d358987480019b8
Tx public key: 0c3794711b3844c2a23f58c4a2ba2abae2bdb3157a861cb69a3c546953a4634a
Timestamp: 1731986724 Timestamp [UCT]: 2024-11-19 03:25:24 Age [y:d:h:m:s]: 00:353:23:45:37
Block: 1156844 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250529 RingCT/type: yes/0
Extra: 010c3794711b3844c2a23f58c4a2ba2abae2bdb3157a861cb69a3c546953a4634a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 527c0173c2647f3a92b5c63fa0cc1a85f132772e0ac39812e425facbedb07d62 0.600000000000 1642467 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": 1156854, "vin": [ { "gen": { "height": 1156844 } } ], "vout": [ { "amount": 600000000, "target": { "key": "527c0173c2647f3a92b5c63fa0cc1a85f132772e0ac39812e425facbedb07d62" } } ], "extra": [ 1, 12, 55, 148, 113, 27, 56, 68, 194, 162, 63, 88, 196, 162, 186, 42, 186, 226, 189, 179, 21, 122, 134, 28, 182, 154, 60, 84, 105, 83, 164, 99, 74, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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