Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5f5b6e27171a917aa9a280ffe234da296c0e044c8236955f95f04a9bf31a916

Tx prefix hash: e3240bea784db1ad82274b293301fbefaa30bc80f7a2ad0071f6c468315a6b0c
Tx public key: 1d0658121e125ff77a14ac9ca6aae145e3ee62a8860fa7a491a7fac92f1a710e
Timestamp: 1699058610 Timestamp [UCT]: 2023-11-04 00:43:30 Age [y:d:h:m:s]: 01:088:04:37:20
Block: 884148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323987 RingCT/type: yes/0
Extra: 011d0658121e125ff77a14ac9ca6aae145e3ee62a8860fa7a491a7fac92f1a710e02110000000933af99f4000000000000000000

1 output(s) for total of 0.721856141000 dcy

stealth address amount amount idx
00: ba5c83cbd5695900dc91fc5bfeed12c9de64358381423ba82508d6ba4994cdbe 0.721856141000 1339881 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": 884158, "vin": [ { "gen": { "height": 884148 } } ], "vout": [ { "amount": 721856141, "target": { "key": "ba5c83cbd5695900dc91fc5bfeed12c9de64358381423ba82508d6ba4994cdbe" } } ], "extra": [ 1, 29, 6, 88, 18, 30, 18, 95, 247, 122, 20, 172, 156, 166, 170, 225, 69, 227, 238, 98, 168, 134, 15, 167, 164, 145, 167, 250, 201, 47, 26, 113, 14, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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