Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbe99ea9ec9b4db8cda4e0e793579bd926d6187a09c0e13c7cc9cb07329f9ba8

Tx prefix hash: 5f3686878adfc75e8f0705499c06662b185923d6121b9e05f69c7434f8de13c8
Tx public key: 95acd47b7c4ed10af56084a5d9051816ee5050e5b64080ed98bd55ddbe59e649
Timestamp: 1718432717 Timestamp [UCT]: 2024-06-15 06:25:17 Age [y:d:h:m:s]: 01:200:16:36:33
Block: 1044575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402055 RingCT/type: yes/0
Extra: 0195acd47b7c4ed10af56084a5d9051816ee5050e5b64080ed98bd55ddbe59e6490211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ec7bafaeb25c86f083dc848ae7669c8a5edceea80a5b757aac3d9f4e77535ce 0.600000000000 1513918 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": 1044585, "vin": [ { "gen": { "height": 1044575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ec7bafaeb25c86f083dc848ae7669c8a5edceea80a5b757aac3d9f4e77535ce" } } ], "extra": [ 1, 149, 172, 212, 123, 124, 78, 209, 10, 245, 96, 132, 165, 217, 5, 24, 22, 238, 80, 80, 229, 182, 64, 128, 237, 152, 189, 85, 221, 190, 89, 230, 73, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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