Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 730aed64e7a814c9bf3df34a56e11012eb84ae52a001a6d48ef5a8702d614222

Tx prefix hash: e5ab7dc5b5f82b6920cf99878a84aff3e06230d73dc75d71f0b83bcfbae51bd9
Tx public key: c7405eeb8f62f7fcccb6148641d34b249d56425519afc9caaa0573baecb22119
Timestamp: 1726545692 Timestamp [UCT]: 2024-09-17 04:01:32 Age [y:d:h:m:s]: 00:204:03:17:05
Block: 1111819 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145730 RingCT/type: yes/0
Extra: 01c7405eeb8f62f7fcccb6148641d34b249d56425519afc9caaa0573baecb2211902110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e3c054dbec1eec60f8b7224eeb0a5c5c18c6022831ae95d3a03580def982553 0.600000000000 1590914 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": 1111829, "vin": [ { "gen": { "height": 1111819 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e3c054dbec1eec60f8b7224eeb0a5c5c18c6022831ae95d3a03580def982553" } } ], "extra": [ 1, 199, 64, 94, 235, 143, 98, 247, 252, 204, 182, 20, 134, 65, 211, 75, 36, 157, 86, 66, 85, 25, 175, 201, 202, 170, 5, 115, 186, 236, 178, 33, 25, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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