Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ebb2ce08baa04b6ff93f118840e343984bc7fb3334203543ec50823fc59e953

Tx prefix hash: 301394e445b2e631c42c1db503945148887ca51e5154e4ed5eef3886bcb3a554
Tx public key: f8079c209c6980787f0beec58f0fbadcd04e14efbe3c1c5b2df34cd9a5dcbcf7
Timestamp: 1723712614 Timestamp [UCT]: 2024-08-15 09:03:34 Age [y:d:h:m:s]: 00:304:20:43:13
Block: 1088341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217696 RingCT/type: yes/0
Extra: 01f8079c209c6980787f0beec58f0fbadcd04e14efbe3c1c5b2df34cd9a5dcbcf7021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aea1cbd7426f4bd088c6a0f1d17c16568e984b52f522b40970842b6ad01ad760 0.600000000000 1562956 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": 1088351, "vin": [ { "gen": { "height": 1088341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aea1cbd7426f4bd088c6a0f1d17c16568e984b52f522b40970842b6ad01ad760" } } ], "extra": [ 1, 248, 7, 156, 32, 156, 105, 128, 120, 127, 11, 238, 197, 143, 15, 186, 220, 208, 78, 20, 239, 190, 60, 28, 91, 45, 243, 76, 217, 165, 220, 188, 247, 2, 17, 0, 0, 0, 4, 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