Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 924765923a916f1d8091b93a6c822b2835ddf74ebe0831c7a27a743648dac85c

Tx prefix hash: 365db210bee2954e45919adad981e52a4c221c281e508d124e7e17980c402301
Tx public key: 2c86f8d656e7edf616ca0c6b14a46e6d885e4968ccda7bb84f9782f581f8a0da
Timestamp: 1762045133 Timestamp [UCT]: 2025-11-02 00:58:53 Age [y:d:h:m:s]: 00:007:06:42:51
Block: 1403004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5214 RingCT/type: yes/0
Extra: 012c86f8d656e7edf616ca0c6b14a46e6d885e4968ccda7bb84f9782f581f8a0da021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aeb01714961b06956e2596673134a0c193cf9d85aa18b3aeccd9aa1a6a966cfc 0.600000000000 1891331 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": 1403014, "vin": [ { "gen": { "height": 1403004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aeb01714961b06956e2596673134a0c193cf9d85aa18b3aeccd9aa1a6a966cfc" } } ], "extra": [ 1, 44, 134, 248, 214, 86, 231, 237, 246, 22, 202, 12, 107, 20, 164, 110, 109, 136, 94, 73, 104, 204, 218, 123, 184, 79, 151, 130, 245, 129, 248, 160, 218, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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