Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cf5f928dd8b6fa6ace1b1cb2a74db47d7e5946099b2d6348f50a76a73691dcf

Tx prefix hash: 5e7c2a5d3e1600fb23ac4d78965a2f8aad64ee168e6279f675fef1aecbd7a5b5
Tx public key: 004cd94a4d611cae795f4c2ff0558d6c4d0f7f1de840913d934271875ead61c9
Timestamp: 1744668955 Timestamp [UCT]: 2025-04-14 22:15:55 Age [y:d:h:m:s]: 00:219:19:26:14
Block: 1261559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154830 RingCT/type: yes/0
Extra: 01004cd94a4d611cae795f4c2ff0558d6c4d0f7f1de840913d934271875ead61c9021100000002dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b7a1be85ea3b50a534a969d377bc421aa4998b9fcc8f49720e8afe97a492cf1 0.600000000000 1748732 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": 1261569, "vin": [ { "gen": { "height": 1261559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b7a1be85ea3b50a534a969d377bc421aa4998b9fcc8f49720e8afe97a492cf1" } } ], "extra": [ 1, 0, 76, 217, 74, 77, 97, 28, 174, 121, 95, 76, 47, 240, 85, 141, 108, 77, 15, 127, 29, 232, 64, 145, 61, 147, 66, 113, 135, 94, 173, 97, 201, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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