Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a4af1ad7da184f0c71b89b7008b54761efc9f276471e05f4777c47243a745b9

Tx prefix hash: fd3fe5542420d7d43e7f8aeeb9e2da5c44f7a808c4a79226b4011afbf1378a0e
Tx public key: ece9bfb0dbbd0a6491bf9f246c077fdf944fc373c1ea5cadc9f9e53fd1baabd3
Timestamp: 1714823522 Timestamp [UCT]: 2024-05-04 11:52:02 Age [y:d:h:m:s]: 00:194:07:08:28
Block: 1014649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139075 RingCT/type: yes/0
Extra: 01ece9bfb0dbbd0a6491bf9f246c077fdf944fc373c1ea5cadc9f9e53fd1baabd30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f564917952dfefa60da913ce502c9c6c65500dd94a4f8a39a09821655ecb37e 0.600000000000 1477798 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": 1014659, "vin": [ { "gen": { "height": 1014649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f564917952dfefa60da913ce502c9c6c65500dd94a4f8a39a09821655ecb37e" } } ], "extra": [ 1, 236, 233, 191, 176, 219, 189, 10, 100, 145, 191, 159, 36, 108, 7, 127, 223, 148, 79, 195, 115, 193, 234, 92, 173, 201, 249, 229, 63, 209, 186, 171, 211, 2, 17, 0, 0, 0, 1, 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