Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 723e5f2b90b30229a05910f44c17b9908fcf93355a6a510f95d24efb61d46371

Tx prefix hash: 31f30e3dc38e9ac4eca811e71f26886cd2a95a3103e8815486cfbc823140b399
Tx public key: 1ca5c07c34e442a24533a372f646b4be11661f625f0a977f2c69a701c2f5c9e2
Timestamp: 1708364620 Timestamp [UCT]: 2024-02-19 17:43:40 Age [y:d:h:m:s]: 01:118:12:18:36
Block: 961089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345667 RingCT/type: yes/0
Extra: 011ca5c07c34e442a24533a372f646b4be11661f625f0a977f2c69a701c2f5c9e202110000000e0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b5e3650478a5bd95604740a3ea9f8ab957fd6ded975944dd19b750faa29c4b3 0.600000000000 1420676 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": 961099, "vin": [ { "gen": { "height": 961089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b5e3650478a5bd95604740a3ea9f8ab957fd6ded975944dd19b750faa29c4b3" } } ], "extra": [ 1, 28, 165, 192, 124, 52, 228, 66, 162, 69, 51, 163, 114, 246, 70, 180, 190, 17, 102, 31, 98, 95, 10, 151, 127, 44, 105, 167, 1, 194, 245, 201, 226, 2, 17, 0, 0, 0, 14, 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