Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4b41ed8b611cd665eb2413da95af32c505e7099b16f1703c77591eb79a79c55

Tx prefix hash: 22d274446d7d26c7a81fa06c5c882044d5fb9aa3412d98c01f1b0e45362fdff2
Tx public key: e93a30ef11e74faec7fd8584bc51d350dd79a3b6a66e82e9922a370dc885a806
Timestamp: 1712843093 Timestamp [UCT]: 2024-04-11 13:44:53 Age [y:d:h:m:s]: 00:338:21:15:10
Block: 998195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242308 RingCT/type: yes/0
Extra: 01e93a30ef11e74faec7fd8584bc51d350dd79a3b6a66e82e9922a370dc885a8060211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f50878030c75009c1446ae020bd1b7f3cffa11d6c353f9ab2bc7494e32c9e6a8 0.600000000000 1458639 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": 998205, "vin": [ { "gen": { "height": 998195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f50878030c75009c1446ae020bd1b7f3cffa11d6c353f9ab2bc7494e32c9e6a8" } } ], "extra": [ 1, 233, 58, 48, 239, 17, 231, 79, 174, 199, 253, 133, 132, 188, 81, 211, 80, 221, 121, 163, 182, 166, 110, 130, 233, 146, 42, 55, 13, 200, 133, 168, 6, 2, 17, 0, 0, 0, 5, 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