Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864fa141112a9ff645a0f520ed16d0986a7b35291d7a9c0493fed186eb31e2d1

Tx prefix hash: dd8307a0f6366a8cb36aafd74b4f0816201c4ce26f317dfaf15276b5b72b7de5
Tx public key: 40577c0f877aecaa67222ea64a45192dcb66c21028bd919ae1a718bbef533435
Timestamp: 1689836035 Timestamp [UCT]: 2023-07-20 06:53:55 Age [y:d:h:m:s]: 01:176:00:00:57
Block: 807739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387124 RingCT/type: yes/0
Extra: 0140577c0f877aecaa67222ea64a45192dcb66c21028bd919ae1a718bbef53343502110000000933af99f4000000000000000000

1 output(s) for total of 1.293080323000 dcy

stealth address amount amount idx
00: 199a8efb87c64aaf28601b62a436d0db2992901df47f11cdd05e7ed71e4ecd82 1.293080323000 1259294 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": 807749, "vin": [ { "gen": { "height": 807739 } } ], "vout": [ { "amount": 1293080323, "target": { "key": "199a8efb87c64aaf28601b62a436d0db2992901df47f11cdd05e7ed71e4ecd82" } } ], "extra": [ 1, 64, 87, 124, 15, 135, 122, 236, 170, 103, 34, 46, 166, 74, 69, 25, 45, 203, 102, 194, 16, 40, 189, 145, 154, 225, 167, 24, 187, 239, 83, 52, 53, 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