Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d9eaddc46210fe7004edf159ae7e57f5ee1e1a140a3e6bccb2dbc06856a144b

Tx prefix hash: 05627e07144e6ff17821bfb0cbaae19e246516823d947a47d332ae035b7da8e1
Tx public key: 94882d037417797376e6b47edac52e3aded27d4cf7e91c73ad5fd70426bbf231
Timestamp: 1765191262 Timestamp [UCT]: 2025-12-08 10:54:22 Age [y:d:h:m:s]: 00:047:20:15:05
Block: 1429081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34070 RingCT/type: yes/0
Extra: 0194882d037417797376e6b47edac52e3aded27d4cf7e91c73ad5fd70426bbf231021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c07669d7233b8d7c2649dcf747e8551e54a3f9972a41bebdeba0b02184a95364 0.600000000000 1917804 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": 1429091, "vin": [ { "gen": { "height": 1429081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c07669d7233b8d7c2649dcf747e8551e54a3f9972a41bebdeba0b02184a95364" } } ], "extra": [ 1, 148, 136, 45, 3, 116, 23, 121, 115, 118, 230, 180, 126, 218, 197, 46, 58, 222, 210, 125, 76, 247, 233, 28, 115, 173, 95, 215, 4, 38, 187, 242, 49, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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