Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cf8702c7b537e1519a046e00a8784aa7a987e4c292e9bf95eb71603129154e6

Tx prefix hash: c699fb007cb877da419e94c0c24f3c2c6bccecd47710b7e5dfb552170d9a7e04
Tx public key: 08bf8dd3461777a4b05c5317dbbdc6fff6854539e11ff738dbd7b5d41bb92a25
Timestamp: 1745678380 Timestamp [UCT]: 2025-04-26 14:39:40 Age [y:d:h:m:s]: 00:209:00:45:36
Block: 1269933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147100 RingCT/type: yes/0
Extra: 0108bf8dd3461777a4b05c5317dbbdc6fff6854539e11ff738dbd7b5d41bb92a25021100000002dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f95fc3e0fb745ee9faa4193faf495d6a0e89d6b1229fb3dd0dc3cbd1c79037ee 0.600000000000 1757172 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": 1269943, "vin": [ { "gen": { "height": 1269933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f95fc3e0fb745ee9faa4193faf495d6a0e89d6b1229fb3dd0dc3cbd1c79037ee" } } ], "extra": [ 1, 8, 191, 141, 211, 70, 23, 119, 164, 176, 92, 83, 23, 219, 189, 198, 255, 246, 133, 69, 57, 225, 31, 247, 56, 219, 215, 181, 212, 27, 185, 42, 37, 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