Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a2cbab8d87281bc41b339229dbbad5c7dd6fafe1cb167be8b4247aa0e16204f

Tx prefix hash: 3e55dee2d9a40115d0a55f1b23000fd414dbe35536036f7bcc2a8a2f84a48134
Tx public key: 54cb491f64a98fb4148047713e6941351714f9e94ec15b250da150429b6bd994
Timestamp: 1706170132 Timestamp [UCT]: 2024-01-25 08:08:52 Age [y:d:h:m:s]: 01:103:01:59:18
Block: 942867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334789 RingCT/type: yes/0
Extra: 0154cb491f64a98fb4148047713e6941351714f9e94ec15b250da150429b6bd9940211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8ff111af1f4b75d49818f3c3ad2b1e02b5c3cb22da8b8b9ccfa6cd1b0cb5369 0.600000000000 1401047 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": 942877, "vin": [ { "gen": { "height": 942867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8ff111af1f4b75d49818f3c3ad2b1e02b5c3cb22da8b8b9ccfa6cd1b0cb5369" } } ], "extra": [ 1, 84, 203, 73, 31, 100, 169, 143, 180, 20, 128, 71, 113, 62, 105, 65, 53, 23, 20, 249, 233, 78, 193, 91, 37, 13, 161, 80, 66, 155, 107, 217, 148, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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