Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdc942e648575cb98c49027907e9b407efcd02b7a043fc1d5299ca7d756953ff

Tx prefix hash: a0ca18c1f28ea81dffc5f13b9e032451047c5dd62c52cdf81bb9b0d107d9a5a0
Tx public key: a88bc7dbbe315fb467def8fa19170d8948febf48c3b043e9c3bf4103cd30a177
Timestamp: 1757261761 Timestamp [UCT]: 2025-09-07 16:16:01 Age [y:d:h:m:s]: 00:116:17:42:24
Block: 1363468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83488 RingCT/type: yes/0
Extra: 01a88bc7dbbe315fb467def8fa19170d8948febf48c3b043e9c3bf4103cd30a177021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f950b44cb3a18b2cc5630fcfa2e54b474137520b9b1a56044d347fbae2603ccd 0.600000000000 1851507 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": 1363478, "vin": [ { "gen": { "height": 1363468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f950b44cb3a18b2cc5630fcfa2e54b474137520b9b1a56044d347fbae2603ccd" } } ], "extra": [ 1, 168, 139, 199, 219, 190, 49, 95, 180, 103, 222, 248, 250, 25, 23, 13, 137, 72, 254, 191, 72, 195, 176, 67, 233, 195, 191, 65, 3, 205, 48, 161, 119, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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