Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3fd092e2ed6592dea9eb72cb8af516fe69fae99701611ce694495be950ce4de

Tx prefix hash: aa7388b9a6c5c6b2a1f6dd9a5603cb25849d76a16aa5182a4eef092eeeb1a90d
Tx public key: c9d174afd7f0ad5c1bfcc1c10c104ff756708c2e3a62eb300bdb2a2711041687
Timestamp: 1728915188 Timestamp [UCT]: 2024-10-14 14:13:08 Age [y:d:h:m:s]: 00:178:08:36:45
Block: 1131474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127244 RingCT/type: yes/0
Extra: 01c9d174afd7f0ad5c1bfcc1c10c104ff756708c2e3a62eb300bdb2a2711041687021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0758c7a58cecb060c364e79a3af8e9fcd015f7ecde32b721da725cdf5db89849 0.600000000000 1614377 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": 1131484, "vin": [ { "gen": { "height": 1131474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0758c7a58cecb060c364e79a3af8e9fcd015f7ecde32b721da725cdf5db89849" } } ], "extra": [ 1, 201, 209, 116, 175, 215, 240, 173, 92, 27, 252, 193, 193, 12, 16, 79, 247, 86, 112, 140, 46, 58, 98, 235, 48, 11, 219, 42, 39, 17, 4, 22, 135, 2, 17, 0, 0, 0, 17, 233, 20, 221, 21, 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