Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a26c19e315430694a4cdc091fe318b5de8f80cf8c9cb9163ad03876dbe6501ff

Tx prefix hash: a2ed92113f032ce94d6e55217820f6a2bdf028eba514dd3923dd0e7efc77775d
Tx public key: 9cd50b6551c1ad4a2479439b42c8e18244f44ada543232fd6ca317443bb6ae4f
Timestamp: 1714493507 Timestamp [UCT]: 2024-04-30 16:11:47 Age [y:d:h:m:s]: 00:342:09:36:27
Block: 1011901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244748 RingCT/type: yes/0
Extra: 019cd50b6551c1ad4a2479439b42c8e18244f44ada543232fd6ca317443bb6ae4f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27626e28ea1ba2f88386cfae2e2f5ee7dac892ee79b73a2e725ba62f65c7b183 0.600000000000 1474259 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": 1011911, "vin": [ { "gen": { "height": 1011901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27626e28ea1ba2f88386cfae2e2f5ee7dac892ee79b73a2e725ba62f65c7b183" } } ], "extra": [ 1, 156, 213, 11, 101, 81, 193, 173, 74, 36, 121, 67, 155, 66, 200, 225, 130, 68, 244, 74, 218, 84, 50, 50, 253, 108, 163, 23, 68, 59, 182, 174, 79, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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