Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df579e299ce31e40588d3424c0fce19feba30b82a8f2e6b5f737d557993a507e

Tx prefix hash: e3a11e5d0555222a38cf8013f96ae89aad4bc8a77cad64dc5b85015c7d908675
Tx public key: b6cec277cb4e7f391dcc6aa940b3f14a424b9270c6c71e51b2e859b13b5442be
Timestamp: 1684641783 Timestamp [UCT]: 2023-05-21 04:03:03 Age [y:d:h:m:s]: 02:169:20:36:32
Block: 764673 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 641177 RingCT/type: yes/0
Extra: 01b6cec277cb4e7f391dcc6aa940b3f14a424b9270c6c71e51b2e859b13b5442be02110000000233af99f4000000000000000000

1 output(s) for total of 1.796061079000 dcy

stealth address amount amount idx
00: ca683315f1a4ed2ee3454e62ab0f0e0d37a7d2ff5545f05cf49e9d5b116c8c6b 1.796061079000 1213618 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": 764683, "vin": [ { "gen": { "height": 764673 } } ], "vout": [ { "amount": 1796061079, "target": { "key": "ca683315f1a4ed2ee3454e62ab0f0e0d37a7d2ff5545f05cf49e9d5b116c8c6b" } } ], "extra": [ 1, 182, 206, 194, 119, 203, 78, 127, 57, 29, 204, 106, 169, 64, 179, 241, 74, 66, 75, 146, 112, 198, 199, 30, 81, 178, 232, 89, 177, 59, 84, 66, 190, 2, 17, 0, 0, 0, 2, 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