Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 341c96b9bc6225dbe1fdaf7393ce546f7c84109ac4627d46638f6886b8fc2ce8

Tx prefix hash: e73a34ddea7779a3b048fb3bd1e5f53670e1287070c01b6d2f83979d0de42359
Tx public key: 7d193b299911ae933436faf66a905bd1d1d9787798e5720cfdd3ccd14df57699
Timestamp: 1730166026 Timestamp [UCT]: 2024-10-29 01:40:26 Age [y:d:h:m:s]: 00:179:17:47:38
Block: 1141781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128298 RingCT/type: yes/0
Extra: 017d193b299911ae933436faf66a905bd1d1d9787798e5720cfdd3ccd14df57699021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f88b67e4aac177f0a0b0382f219f623845ce921c804938e0fef816408d5f39f 0.600000000000 1625610 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": 1141791, "vin": [ { "gen": { "height": 1141781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f88b67e4aac177f0a0b0382f219f623845ce921c804938e0fef816408d5f39f" } } ], "extra": [ 1, 125, 25, 59, 41, 153, 17, 174, 147, 52, 54, 250, 246, 106, 144, 91, 209, 209, 217, 120, 119, 152, 229, 114, 12, 253, 211, 204, 209, 77, 245, 118, 153, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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