Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edeb4b2046775274a488cdb9e697a241ca12fcc72cba3fee06732650d890c687

Tx prefix hash: 3bb94b85375c119db87ac81c673d924180c1e2e989a7f0f0289c21168c591adf
Tx public key: 774f1ecf596a1bbfd2e5349fb1ac545435f7f6dec26922b0f90e747d4a852de7
Timestamp: 1720464808 Timestamp [UCT]: 2024-07-08 18:53:28 Age [y:d:h:m:s]: 00:200:05:48:49
Block: 1061413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143238 RingCT/type: yes/0
Extra: 01774f1ecf596a1bbfd2e5349fb1ac545435f7f6dec26922b0f90e747d4a852de7021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f47b0b5f833a2d5a48be1d02543989bc643725701aafa43e63f815011409fcc 0.600000000000 1531904 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": 1061423, "vin": [ { "gen": { "height": 1061413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f47b0b5f833a2d5a48be1d02543989bc643725701aafa43e63f815011409fcc" } } ], "extra": [ 1, 119, 79, 30, 207, 89, 106, 27, 191, 210, 229, 52, 159, 177, 172, 84, 84, 53, 247, 246, 222, 194, 105, 34, 176, 249, 14, 116, 125, 74, 133, 45, 231, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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