Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01439c356c1a6b4b6732c661f594432efd77f8192fee1fcd4c65dbeaac643fc5

Tx prefix hash: cf3ac0a3ae77d89c467cb7597e3c4d302f580bf2e615b22f38c3accd9797c20a
Tx public key: e81086309f493f2894c1464623d287d5cbe909ae800ab54d9fec923f35a21389
Timestamp: 1714079309 Timestamp [UCT]: 2024-04-25 21:08:29 Age [y:d:h:m:s]: 00:202:12:53:44
Block: 1008460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144996 RingCT/type: yes/0
Extra: 01e81086309f493f2894c1464623d287d5cbe909ae800ab54d9fec923f35a213890211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f22283a48ecb66926e0db76ac44363488194fd5074ab03a8f317122a717fb92 0.600000000000 1469930 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": 1008470, "vin": [ { "gen": { "height": 1008460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f22283a48ecb66926e0db76ac44363488194fd5074ab03a8f317122a717fb92" } } ], "extra": [ 1, 232, 16, 134, 48, 159, 73, 63, 40, 148, 193, 70, 70, 35, 210, 135, 213, 203, 233, 9, 174, 128, 10, 181, 77, 159, 236, 146, 63, 53, 162, 19, 137, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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