Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63251da1d1974672b3bc5a3bf16a4e917060792d984509bee62d020d468c0381

Tx prefix hash: cd5b56d0cab96d30c9415078c8c9fa362b182698f9224ad0b360ae67759a5f96
Tx public key: c0a5fa8af15cba011a8f6a4a0f884aed1cd2987a912fd1a699af05cd729472f1
Timestamp: 1708650249 Timestamp [UCT]: 2024-02-23 01:04:09 Age [y:d:h:m:s]: 01:120:14:15:47
Block: 963461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347072 RingCT/type: yes/0
Extra: 01c0a5fa8af15cba011a8f6a4a0f884aed1cd2987a912fd1a699af05cd729472f102110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f434d2fa4de0f7528ee27cf186292911069e9b0b7bc027bbf940f7317bf05251 0.600000000000 1423172 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": 963471, "vin": [ { "gen": { "height": 963461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f434d2fa4de0f7528ee27cf186292911069e9b0b7bc027bbf940f7317bf05251" } } ], "extra": [ 1, 192, 165, 250, 138, 241, 92, 186, 1, 26, 143, 106, 74, 15, 136, 74, 237, 28, 210, 152, 122, 145, 47, 209, 166, 153, 175, 5, 205, 114, 148, 114, 241, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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