Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bd450c67fc0c864fca5b901aa463ff1fe3577804c2855da8ff72d1836b0193c

Tx prefix hash: f7d44ce24191135b0937d4a8bb57cb7de3523a29f276179215d53388ee0b74f5
Tx public key: ce46f5847b81b2b89d11997d5bfef17a7e50dc633fdbd1a11a2625b5f826130b
Timestamp: 1726757549 Timestamp [UCT]: 2024-09-19 14:52:29 Age [y:d:h:m:s]: 00:069:20:20:18
Block: 1113580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49927 RingCT/type: yes/0
Extra: 01ce46f5847b81b2b89d11997d5bfef17a7e50dc633fdbd1a11a2625b5f826130b021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2df7bbb94a7a126c807f9c18e2bd2ad77038a40413b50c76b937538c2228868c 0.600000000000 1593303 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": 1113590, "vin": [ { "gen": { "height": 1113580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2df7bbb94a7a126c807f9c18e2bd2ad77038a40413b50c76b937538c2228868c" } } ], "extra": [ 1, 206, 70, 245, 132, 123, 129, 178, 184, 157, 17, 153, 125, 91, 254, 241, 122, 126, 80, 220, 99, 63, 219, 209, 161, 26, 38, 37, 181, 248, 38, 19, 11, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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