Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dab4920d18bc365d828b7e706c054fd543c90c955410b9abd2ff8b6134086c53

Tx prefix hash: 530f0f4f2a9e34266cb23579346f56a76bb3b69606db8e83daec1842ba188895
Tx public key: d07a509c7665486f4208b81071e5c5f28394ecf0b4fb04555154066e3d417679
Timestamp: 1723243662 Timestamp [UCT]: 2024-08-09 22:47:42 Age [y:d:h:m:s]: 00:299:22:05:25
Block: 1084448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214277 RingCT/type: yes/0
Extra: 01d07a509c7665486f4208b81071e5c5f28394ecf0b4fb04555154066e3d41767902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ab1cd37c0ae5eb910ae9f62e3fb32eba5c865f37fd1b94ce008960b656d56aa 0.600000000000 1558729 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": 1084458, "vin": [ { "gen": { "height": 1084448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ab1cd37c0ae5eb910ae9f62e3fb32eba5c865f37fd1b94ce008960b656d56aa" } } ], "extra": [ 1, 208, 122, 80, 156, 118, 101, 72, 111, 66, 8, 184, 16, 113, 229, 197, 242, 131, 148, 236, 240, 180, 251, 4, 85, 81, 84, 6, 110, 61, 65, 118, 121, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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