Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b046bead3c276e0cfa319e9fcbaba488d4970e9cc2b51e5b8af2f6dd0bcee148

Tx prefix hash: fd042550e1aaefdb963d0f5bed0204ac3d0802638839020bdd1e56fa460cfb4d
Tx public key: ea35d20f4e14d466b9d1cb2e764ab1c9dbd1a33b82e7ca56f03b676cb0120b77
Timestamp: 1685447542 Timestamp [UCT]: 2023-05-30 11:52:22 Age [y:d:h:m:s]: 01:170:15:38:08
Block: 771353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383349 RingCT/type: yes/0
Extra: 01ea35d20f4e14d466b9d1cb2e764ab1c9dbd1a33b82e7ca56f03b676cb0120b77021100000001b3164c24000000000000000000

1 output(s) for total of 1.706819040000 dcy

stealth address amount amount idx
00: f6b6e6f1349a4bba69788a06d45747372e49d4dcfc0eecb68941eacbdad743a9 1.706819040000 1220706 of 0

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": 771363, "vin": [ { "gen": { "height": 771353 } } ], "vout": [ { "amount": 1706819040, "target": { "key": "f6b6e6f1349a4bba69788a06d45747372e49d4dcfc0eecb68941eacbdad743a9" } } ], "extra": [ 1, 234, 53, 210, 15, 78, 20, 212, 102, 185, 209, 203, 46, 118, 74, 177, 201, 219, 209, 163, 59, 130, 231, 202, 86, 240, 59, 103, 108, 176, 18, 11, 119, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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