Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e233ea20f18f852aa0c3b55e8f7716910a7b0e79f3237152ddf94c0ef133e451

Tx prefix hash: 33a97a79c7bf339ca7a8a93947e293e0c58e446570f9029555a653c8c59f4b27
Tx public key: 630bb44e6b5539c5f7d9c00365df7e2fddd595ce433f05ea7ac3dbf734898353
Timestamp: 1719971460 Timestamp [UCT]: 2024-07-03 01:51:00 Age [y:d:h:m:s]: 00:263:01:07:17
Block: 1057313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187956 RingCT/type: yes/0
Extra: 01630bb44e6b5539c5f7d9c00365df7e2fddd595ce433f05ea7ac3dbf734898353021100000003ddd3db91000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b676b2722fde0a2ae60c5ddf9bba227aa470877575fda566e91b43459256ffbb 0.600000000000 1527748 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": 1057323, "vin": [ { "gen": { "height": 1057313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b676b2722fde0a2ae60c5ddf9bba227aa470877575fda566e91b43459256ffbb" } } ], "extra": [ 1, 99, 11, 180, 78, 107, 85, 57, 197, 247, 217, 192, 3, 101, 223, 126, 47, 221, 213, 149, 206, 67, 63, 5, 234, 122, 195, 219, 247, 52, 137, 131, 83, 2, 17, 0, 0, 0, 3, 221, 211, 219, 145, 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