Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 531ff432ca526afc10eac37cf936930ed065f92d68abd421921f224178a3bfb1

Tx prefix hash: 378503dcf823e4704fd69980001c0b1b4a07b0cb9a900b5e7baf99d01bc009b2
Tx public key: 194619c7e68da29e72964a6775e9ab55e4ff3d842dc6a1f18b1cb269cfb57172
Timestamp: 1732191652 Timestamp [UCT]: 2024-11-21 12:20:52 Age [y:d:h:m:s]: 00:131:20:46:13
Block: 1158526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94058 RingCT/type: yes/0
Extra: 01194619c7e68da29e72964a6775e9ab55e4ff3d842dc6a1f18b1cb269cfb571720211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92292cbaa680efa69e11a70b73f71cf0672a8c7edfd79f27fceb679573603256 0.600000000000 1644155 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": 1158536, "vin": [ { "gen": { "height": 1158526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92292cbaa680efa69e11a70b73f71cf0672a8c7edfd79f27fceb679573603256" } } ], "extra": [ 1, 25, 70, 25, 199, 230, 141, 162, 158, 114, 150, 74, 103, 117, 233, 171, 85, 228, 255, 61, 132, 45, 198, 161, 241, 139, 28, 178, 105, 207, 181, 113, 114, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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