Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89c58605374dad51af33a9de26cedea7a199986316835a3658300b6d2be6ade0

Tx prefix hash: 6bf1bdd581ead951062bc55f80ce8522881012f719a99db682b06746fb24c53a
Tx public key: 7f63523321cfdca91d84bf4e2a893a9f55f7199f1539dfae8646efde7fef344d
Timestamp: 1696626903 Timestamp [UCT]: 2023-10-06 21:15:03 Age [y:d:h:m:s]: 02:041:15:11:02
Block: 863985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 549387 RingCT/type: yes/0
Extra: 017f63523321cfdca91d84bf4e2a893a9f55f7199f1539dfae8646efde7fef344d021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.841897217000 dcy

stealth address amount amount idx
00: d280fb18f95ca7915ca0f3e3e154951272afa4b3c039dbc782d90b80d82c1055 0.841897217000 1318489 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": 863995, "vin": [ { "gen": { "height": 863985 } } ], "vout": [ { "amount": 841897217, "target": { "key": "d280fb18f95ca7915ca0f3e3e154951272afa4b3c039dbc782d90b80d82c1055" } } ], "extra": [ 1, 127, 99, 82, 51, 33, 207, 220, 169, 29, 132, 191, 78, 42, 137, 58, 159, 85, 247, 25, 159, 21, 57, 223, 174, 134, 70, 239, 222, 127, 239, 52, 77, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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