Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 318dd9de97d18a9b387f8e22fcea2ff7937d87ab6b1478ea11376efda55df5f0

Tx prefix hash: 2751bfecb5567b44402850e2ab57c9c3599c3bea1db740b4d0d4f0ba211e14a9
Tx public key: 344b64269ad7f7f34397da96e712261c5c911d57b1476a83056162d83bc779f5
Timestamp: 1708407276 Timestamp [UCT]: 2024-02-20 05:34:36 Age [y:d:h:m:s]: 01:275:18:54:16
Block: 961444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455863 RingCT/type: yes/0
Extra: 01344b64269ad7f7f34397da96e712261c5c911d57b1476a83056162d83bc779f50211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c20601ec344a1e11c3aa0bf064df80a6e938792bb5a9f4a9fca13ec6f0b9758 0.600000000000 1421053 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": 961454, "vin": [ { "gen": { "height": 961444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c20601ec344a1e11c3aa0bf064df80a6e938792bb5a9f4a9fca13ec6f0b9758" } } ], "extra": [ 1, 52, 75, 100, 38, 154, 215, 247, 243, 67, 151, 218, 150, 231, 18, 38, 28, 92, 145, 29, 87, 177, 71, 106, 131, 5, 97, 98, 216, 59, 199, 121, 245, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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